Alan Lord wrote: > Tijnema ! wrote: <snip> >> So if you start creating a bash file that works for most of the >> packages, with su/suo, you can copy that in every package to be >> automated, and edit it for specific apps that require other configure >> options. > > This is a BAD idea. This was similar in concept to the old nALFS which > required hours of editing and changes each time the book was updated. > JHALFS parses the book and creates the build scripts automatically - no > human mistakes from such things as typing errors are introduced and it > is much quicker!
The only difficulty with JHALFS is if you want to build ALMOST what's in the book. Like, for instance, I don't want the old sysvinit or Berk's DB or Man-db or Syslog, but all the rest please. Now JHALFS isn't so good. JHALFS would be fine if it had some way of integrating a PM, so that you could uninstall the unwanted packages, I guess. R. P.S. Don't you just hate HTML mailings! Even worse than top posting. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
