El Martes, 4 de Septiembre de 2007 22:12, Kevin Williams escribió:
> I've downloaded jhalfs, svn version, rev 3466, to help ease the pain for my
> second build of BLFS.
>
> I've a bunch of questions regarding the working of jhalfs.
>
> 1. Can I build LFS first and then go for BLFS ?
You must build first LFS to can start building BLFS packages on-top of it.
> I mean, can I use different
> jhalfs
> sources for LFS and BLFS or do I have to use the same jhalfs I used for
> both ?
Actually, you will use different sources. With jhalfs you can build
LFS/CLFS/HLFS systems, but BLFS packages are installed using blfs-tool.
blfs-tool is a separate build framework included as a sub-package into jhalfs
but don't depend on jhalfs. jhalfs is able to install blfs-tool as part of a
{,H,C}LFS build (when selecting the "Add blfs-tool support" option) or just
install blfs-tool on a running system (when selecting BLFS as the book to be
built).
> All I'm trying to know is that, can I build LFS and BLFS independently
> of each
> other at least in the matters of jhalfs ?
They are totally independent. There are ways to build both LFS and BLFS at the
same time from the same Makefile, but that is a very advanced topic.
> 2. Can I build BLFS in a chrooted environment ? If not, how or what
> files/config
> do I need to change (a hint shall be enough !). I was thinking of using
> the same
> technique as LFS. Would this lead to any difficulties/complications
> from point
> of view of jhalfs ?
Like has been pointed, looks like only QT have issues when building into a
chroot. Also, I would suggest that the running kernel should be the one to be
used on the final LFS+BLFS system.
>
> 3. Can I stop the build anytime I like and resume from the last known point
> ?
> Or, at least from the last package that was being compiled ?
Yes, but taking care that is you are building into a chroot you must be sure
that the virtual kernel filesystems are mounted before resuming the build.
> 4. Does jhalfs keeps track of installed packages even when I reconfigure
> jhalfs
jhalfs don't track installed packages, blfs-tool does it.
blfs-tool track what BLFS packages has been installed on a previous run to can
skip they from the configuration menu and for the dependencies tree. For each
installed package a empty file is created in $TRACKING_DIR. That file is
named {pkg_id}-{pkg_vrs}, where {pkg_id} is the ID attribute used in the BLFS
XML sources identify the page for that package, and {pkg_vrs} is the version
installed for that package.
> using menuconfig provided I unselect the 'Rebuild files' and leave the
> $TRACKING_DIR intact ?
blfs-tool don't have a "Rebuild files" option. That option is on jhalfs to
automatically clean-up a target directory before start building a new fresh
system.
>
> 5. I need to keep track of the files being installed by each of the package
> individually so I can use a package management tool like paco. How
> do I integrate this into jhalfs ? I mean, is there an easy way of doing
> it
> other than to edit each script manually ?
No easy way to integrate it. Maybe in a future version.
> If a package manager cannot
> be integrated into jhalfs, how I can extract the list of files being
> installed
> by each of the package individually ?
For {,H,C}LFS builds there is a "Log installed files" option that generates
the list of files installed for each package using a find command.
For BLFS you need to insert the appropriate commands for your PM into each
build script.
--
Manuel Canales Esparcia
Usuario de LFS nº2886: http://www.linuxfromscratch.org
LFS en castellano: http://www.escomposlinux.org/lfs-es http://www.lfs-es.info
TLDP-ES: http://es.tldp.org
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
