On 04/23/2012 12:26 AM, Bruce Dubbs wrote: > Ken Moffat wrote: > >> I was going to support Andy's post, but I held back after Thomas >> posted, to give it some more thought. For me, there are two >> problems with the current xorg build: >> >> 1. It's scripted. Scripting is good, and nobody who repeatedly >> builds BLFS (or LFS) can do without it. But we shouldn't be >> spoon-feeding our users! Every builder should be encouraged to >> create their own scripts, to suit what they are doing. In my own >> case, /sources is an nfs mount and I have my own functions to handle >> common tasks and logging. Plus, of course, my own failure modes. >> >> 2. The actual versions of the xorg packages used by any particular >> version of the book are opaque, as is the build order. You have to >> download the wget files to see these. For everything else, you can >> just look at the version in the book. ISTR that the order in which >> the libraries are built has slightly changed over the years. >> >> Certainly, adding a page for each package will make the book a lot >> bigger. But I doubt it will make it a mess. OK, perhaps the video >> drivers are a bit messy (previous item could link to a page listing >> the drivers, each driver could link to what comes after instead of >> the "next" video driver). Also, just because everything was in the >> last non-modular xorg doesn't mean we still need to build it! e.g. >> who really uses the old fonts ? [ /me stands back, ready to warm his >> hands in the flames :) ] > > I respectfully disagree. Having the scripts in the book provide an example > about how to script a build. I don't think we have any other such scripting > examples directly in the book. One could, of course, look at the output of > jhalfs, but having 200+ additional pages in the book would be extremely > tedious > both for us and the user. There are 273 uncommented lines in the wget files. > > I think the scripts are a pragmatic compromise, although we could publish the > wget files in each section instead of getting them from anduin. > > -- Bruce
This might be a good idea actually since you ignored my suggestion to script every chapter. It could be done, but adding several hundreds of pages might not be necesary. It could be done like DBus or Python modules - all on one page. But this one draws some dependency hell. Many packages depend on Xorg Libraries (because all of them are installed at once) and if we split them, we would have to rework all dependencies pointing to individual libraries. Other than that, I see no drawbacks, it can be done. The irony is, there is some guy on LFS IRC telling how Xorg section is confusing, and yes it is for the beginner, it was for me, too! -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
