> > "What I meant was" given Modular XOrg allows various packages to be > > updated independently, at any particular point in time the upstream > > package list may well be different than as in the BLFS book. > > Incorrect. The packages are updated daily for -dev and the stable > releases are there. Since you are doing an odd build based on years > old packages, I think you are using a version of BLFS that is old, but > not a stable release. We did not do BLFS stable between 6.3 and > 7.5 but all
True, I used an old development version of BLFS with contemporaneous package versions that were relevant at the time, but beside the point. And that's quite a long jump, between 6.3 & 7.5 don't you think? > the files for released versions are there: > > http://anduin.linuxfromscratch.org/sources/BLFS/ > > The way > > some sites manage their sources, purging older versions, or may > > choose to, maybe the set in the book will be available or maybe not. > > In part because I'm always "behind", I've had trouble in the past > > finding the right versions of packages. Newer updates may also be > > incompatible with what's in the book. It happens. > > If you stay with stable versions of the book at versions 7.5 and > later, the packages are there. If not, you get to figure it out. You > may be able to find the versions you want in conglomeration/. But they won't be if all the LO, etc., packages as used in the book aren't captured but left to the policies of the upstream sources. What guarantees do we have that what the build script fetches whenever that happens has any correlation to the version of the book being used? I thought that was the point under discussion. Is there some way I could be clearer about this? I did keep everything that was downloaded during/for the LO, OJDK, XOrg, etc., builds. Burning a couple copies on DVDs is easy and negligibly expensive. If it comes to it, I could rebuild this system from scratch without requiring anything from upstream. That's another form of security. > > > Where as, if the package complement given in the book is captured > > and preserved, then the book always works. I like that. -- Paul Rogers [email protected] Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://www.fastmail.com - A fast, anti-spam email service. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
