Changes between Version 14 and Version 15 of WikiStart


Ignore:
Timestamp:
03/21/2013 09:30:37 PM (11 years ago)
Author:
Pierre Labastie
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v14 v15  
    99== What can I do with ALFS? ==
    1010
    11 The goal of ALFS is to automate the process of creating an LFS system. It seeks to make the process of building LFS easier and more efficient while still providing flexibility by granting the user total control and insight into the compilation and management of his LFS build.
     11The goal of ALFS is to automate the process of creating an LFS system. It seeks to follow the book as closely as possible by directly extracting instructions from the XML sources. This is the reason why it may also be used as a test of the current book instructions.
    1212
    1313== How is ALFS implemented? ==
     14The  official implementation of ALFS is called jhalfs. Originally created by Jeremy Huntwork, but since developed and maintained by Manuel Canales Esparcia, George Boudreau, and Thomas Pegg, jhalfs has become a light-weight, practical method of automating an LFS build. jhalfs is a Bash shell script that makes use of Subversion and xsltproc to first download the XML sources of the Linux From Scratch book and then extract any necessary commands, placing them into executable shell scripts. If you do not already have the necessary source packages in place on your system jhalfs can fetch them. Finally, jhalfs generates a Makefile which will control the execution of the shell scripts, allowing for recovery if the build should encounter an error. A way to use package management has been added by Pierre Labastie.
    1415
    15 === nALFS ===
    16 
    17 The first ALFS implementation was nALFS by Neven Has. nALFS is a small program written in C. It first parses an XML profile that contains information concerning the LFS build process into a series of internal commands. It can then execute these at your discretion, thus automating the compilation of LFS.
    18 
    19 === jhalfs ===
    20 
    21 Currently there is a new official implementation of ALFS, called jhalfs. Originally created by Jeremy Huntwork, but since developed and maintained by Manuel Canales Esparcia and George Boudreau, jhalfs has become a light-weight, practical method of automating an LFS build. jhalfs is a Bash shell script that makes use of Subversion and xsltproc to first download the XML sources of the Linux From Scratch book and then extract any necessary commands, placing them into executable shell scripts. If you do not already have the necessary source packages in place on your system jhalfs can fetch them. Finally, jhalfs generates a Makefile which will control the execution of the shell scripts, allowing for recovery if the build should encounter an error. Since jhalfs extracts its commands to run directly from the LFS book, there are no profiles to edit or maintain.
    22 
    23 The most current jhalfs stable release can been downloaded from http://www.linuxfromscratch.org/alfs/downloads/jhalfs/stable/.''
    24 
    25 To use the development version of jhalfs, fetch it via svn with the command:
     16ALFS jhalfs is maintained as a subversion repository. There is only a development version, which you can fetch with the command:
    2617{{{
    2718svn co svn://svn.linuxfromscratch.org/ALFS/jhalfs/trunk jhalfs
    2819}}}
    2920
    30 To know what books versions are supported by each jhalfs version, please see SupportedBooks.
     21An experimental extension of ALFS aimed at automating the building of packages in the BLFS book is maintained separately in the ablfs branch:
     22{{{
     23svn co svn://svn.linuxfromscratch.org/ALFS/jhalfs/branches/ablfs
     24}}}
     25
     26== History ==
     27Before jhalfs, an implementation named nALFS was developped. A more ambitious project, named simply alfs was designed around 2004, but was never pushed to completion.
     28
     29=== nALFS ===
     30The first ALFS implementation was nALFS by Neven Has. nALFS was a small program written in C. It first parsed an XML profile that contained information concerning the LFS build process into a series of internal commands. It could then execute these at your discretion, thus automating the compilation of LFS.
    3131
    3232=== alfs ===
    3333
    34 There are many in-depth features that have been requested for future ALFS implementations. Because of this, development has been slated for an entirely new build tool which will be called alfs. To see a list of features that will appear in alfs, please read our [http://www.linuxfromscratch.org/alfs/view/alfs-srs/alfs-srs.html Software Requirements Specification]. If you wish to help develop this new tool, please subscribe to the alfs-discuss mailing list and leave a note there explaining your desire to help.
     34There were many in-depth features that had been requested for ALFS implementations. Because of this, development had been slated for an entirely new build tool which would have been called alfs. To see a list of features that would have appeared in alfs, please read our [http://www.linuxfromscratch.org/alfs/view/alfs-srs/alfs-srs.html Software Requirements Specification]. Eventually, the ease of use of jhalfs definitely burried the alfs project.
    3535
    3636== Who's who: ==
    … …  
    3939||Developer (jhalfs):||George Boudreau||
    4040||Developer (jhalfs):||Manuel Canales Esparcia||
     41||Developer (jhalfs, ablfs): ||Pierre Labastie||
    4142||Developer (alfs):||Tim Sarbin||
    4243