differences between custom-tools, blfs-tool and blfs-support

George Boudreau georgeb at linuxfromscratch.org
Tue Jun 10 12:16:09 PDT 2008


Benjamin John wrote:
<snip>

> My idea is to create the set of apps from the book I need (lets say 
> KDE-core) with the help of blfs-support and copy the result to the 
> custom tools section of the LFS book (I think there are some 
> modifications necessary)
>>> One difference I saw, is that inside the new system the build process 
>>> runs as user and only the installation is done by root.
>>> What about building after the lfs-scripts (in custom tools)? Is it all 
>>> done by root or all by the specified user?
>> It has been a while since I wrote the 'custom' section. If I am not
>> mistaken it is run under chroot.
> My intention for all this is to get an automated build environment for 
> xLFS plus some extra apps an deviations from the books to build xLFS on 
> different machines (with slightly different makefiles) and to have a 
> tool to test new apps or versions.
> Jhalfs is meant to create the base for this environment and everything 
> else is done by me.
> So the question is, is there a difference (in the "end product", file 
> permissions, linking to the proper libs, etc.) between building the 
> BLFS- and other apps in the custom tool section and building in BLFS 
> support after reboot

Other than you doing all the coding by hand, handling the build order 
and maintaining the patches and tarballs the end result is the same.

::note:: There is an experimental version of jhalfs that uses xml for 
the build description but this version has not been fully tested.
>>    regards,
>>      GeorgeB
>>> Regards
>>> Benjamin
>>
> 




More information about the alfs-discuss mailing list