Archaic wrote:
And there is nothing requiring an imminent release of cross-lfs, either. The idea of getting gcc-4 into trunk post 6.2 sounds good. What really sounds good after that is an i18n cleanup in 6.4 and a merge to cross-lfs when it is done. That said, there is also no technical reason we can't have a 7.0 and a 6.3 out at the same time provided that 7.0 comes with warnings that multilib and 64 bit may not be fully supported in BLFS. Then perhaps a 6.4 and a 7.1 with the i18n cleanup (and various minor package updates as well). After that, the 6.x branch could probably be phased out. All IMO.
I believe I'm pretty much in agreement with all that's been said so far, though I would like to have one point clarified, please. I've heard it said before that major version numbers in LFS were supposed to represent major changes in the toolchain or build method... is that correct? If so, does releasing a LFS book with gcc4, a new binutils, and (hopefully by that time a new glibc) not suggest a new major version number? Or is that all out the window now? Or was I completely misunderstanding the versioning before?
-- JH -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
