On 3/2/07, Matthew Burgess <[EMAIL PROTECTED]> wrote: > On Friday 02 March 2007 11:49, TheOldFellow wrote: > > > 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. > > I'd probably handle this as a locally maintained set of patches on top of the > LFS book, then run jhalfs against that working copy. I don't think you're > going to hit too many merge conflicts with those kind of changes as your > replacement package XML files will obviously be entire files, and > chapter06/chapter06.xml changes very infrequently.
That is absolutely how to do it. This was how I tested the linux headers + needed patches way back. And I think if there's going to be better support in jhalfs in the future for this kind of thing, I think it will probably have to be done at the XSL level. Once you get past that level, it's really ugly to change things around. See the (about to be removed) paco patch in jhalfs. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
