Questions/queries on jhalfs
kevkim55 at gmail.com
Tue Sep 4 18:30:51 PDT 2007
Thanks a zillion Thomas, I really appreciate your help in this regard. :-D
>If you mean using two completely different versions of jhalfs I wouldn't
>recommend that or see it as necessary, since both LFS and BLFS can be
>setup using the same version.
I think, my first question wasn't what it was intended to be. Certainly it
was my fault.
I was trying to know, if I start jhalfs and configure it for BLFS, would it
start with the
commands from BLFS or would it start with LFS and then proceed to BLFS ?
>only one package (namely Qt) has been known not to build
>right in a chroot.
Thanks for the hint ! :-)
>Except if you were to stop it during the chroot phase and then reboot, it
might get a
Again Thanks for the hint ! I see what you mean.
I guess, I should be able to manually chroot and resume make.
>That's what the TRACKING_DIR is for, unless it's cleaned out for some
>reason, jhalfs will know what's installed hopefully.
I read that in README files and it wasn't immediately clear whether this
saved the list of individual files of each package. The README files use
"This tool includes a very simple tracking system to log which packages
installed using the tool". Thus, I couldn't tell if it only saved package
OR tar.gz'd package OR the individual files of a package or their names.
>It's possible, there was a patch to add paco support to jhalfs that was
>included in a few of the past versions of jhalfs, but it wasn't being
>maintained by the person who created it for a while and was eventually
Yeah ! I read that ! What was discussed was about the xsl files. Which would
knowing xls !! I were wondering if I could simply insert a command
somewhere. I guess,
I found a way. It is not so easy and would require editing each of the
scripts and changing
the 'make install' lines. Possibly some scripting using sed can achieve
this. Not sure,
how I could do the same for those packages which, do not include a 'make
install' line and
those which, dynamically create files (convert-mans script which converts
man pages for eg.).
Personally I feel that, package management is necessary keeping in mind,
100's if not 1000's of
files abandoned by packages that were upgraded somewhere along the time.
Without PM, it becomes really difficult to keep track of files which are no
longer needed. I use paco for this. only to keep track of installed files
(for clean removal).
On 9/4/07, Thomas Pegg <thomasp at linuxfromscratch.org> wrote:
> Kevin Williams wrote:
> > 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 ? 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 ?
> > And, is it that, I have to go for BLFS to begin with ? I'm lil'
> > confused here.
> > 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 ?
> If you mean using two completely different versions of jhalfs I wouldn't
> recommend that or see it as necessary, since both LFS and BLFS can be
> setup using the same version.
> > 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 ?
> Of course, many seasoned LFS builders (myself included) do it that way
> all the time, only one package (namely Qt) has been known not to build
> right in a chroot.
> > 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 ?
> Seeing as jhalfs generates a Makefile, it is resumable. Except if you
> were to stop it during the chroot phase and then reboot, it might get a
> little tricky.
> > 4. Does jhalfs keeps track of installed packages even when I reconfigure
> > jhalfs
> > using menuconfig provided I unselect the 'Rebuild files' and leave
> > $TRACKING_DIR intact ? This is because, I want to include lots of
> That's what the TRACKING_DIR is for, unless it's cleaned out for some
> reason, jhalfs will know what's installed hopefully.
> > 5. I need to keep track of the files being installed by each of the
> > individually so I can use a package management tool like paco. How
> It's possible, there was a patch to add paco support to jhalfs that was
> included in a few of the past versions of jhalfs, but it wasn't being
> maintained by the person who created it for a while and was eventually
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the alfs-discuss