> > currently in there, for one more release at minimum. Consistency is the > > thing that is the most important to me, and one more release would also > > give people who use LFS in production the time to adapt their systems > > for the new changes.
I do understand the problem, but I forsee one pretty big hassle forthcoming. The one thing to say about the existing book is: one is quite certain all the packages are consistent with each other. Split in two, or even more (networking & GUI stuff suggests themselves), the idea presents itself: different release readiness for different sections, and separate development tracks probably lead to package version inconsistencies. If one decides to enforce keeping them in-step, what really have you gained? This is somewhat the situation I found when I came aboard with 4.1: BLFS was still 1.0! It jumped from 1.0 to 5.x. Perversely, perhaps one should explode the book altogether! Have each package separate, on its own development track, then have wget and make files. Shift entirely to the sort of thing in the SVN versions. Granted, everybody would likely have a unique system build, making support very troublesone. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
