Jim Gifford wrote:
I would like at this time to propose that we create a separate project for Cross-LFS, like ALFS, HLFS and BLFS. There are many reasons for wanting to do so:
Agreed in priniciple, though I have a couple of nits to pick...
Why waste the LFS community's time searching for a bug in the build process when it is a Cross-LFS bug only? Cross-LFS will tend to see more build issues due to its build nature; LFS can then investigate to see what affects them.
I'd rather see this investigation instigated from the Cross-LFS side of things to be honest. You can't expect all of lfs-dev to subscribe to cross-lfs-dev (or whatever), and therefore I'll go out on a limb and say it would be fairer if cross-lfs devs post any potential issues with LFS' toolchain/build process to lfs-dev. We'll then of course endeavour to investigate the problem to see if it does indeed affect us, and if cross-lfs can reduce things down to a minimal testcase that demonstrates the problem, so much the better.
Cons:
The cons you give appear to be cons of the cross-lfs book itself, not of moving the book out from a branch to a project in its own right. i.e. I don't see any cons with the move at all :)
Regards, Matt. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
