Jim Gifford wrote:
Development of the rules will need to submitted into a common svn, that
will need to be created.
I'm going to do a complete about-turn on my earlier message from
tonight. The way I see it is that the current svn layout and procedures
around them should work just fine:
LFS/trunk/BOOK - LFS book, forms the base of CLFS, BLFS, etc.
LFS/trunk/bootscripts - LFS bootscripts, forms the base on which BLFS
and CLFS bootscripts are built on.
LFS/trunk/udev-config - LFS udev rules, forms the base on which BLFS and
CLFS udev rules are built on.
Now, if BLFS and/or CLFS need bootscript tarballs and udev-config
tarballs automatically generated to facilitate them getting access to
bug-fixes and/or feature enhancements from LFS in a timely fashion I'm
sure that can be setup relatively easily.
The major advantage to this scheme, IMO, is consistency. Everything to
do with the LFS book is in one repository. Likewise, for BLFS and CLFS,
everything concerning their books would be in their own svn repos. If
you need changes to the LFS bootscripts or rules files submit a trac
ticket just as is done now and it'll be dealt with. No changes to
current procedures are required, from what I can see.
So, what are the drawbacks to this approach? Why won't it work?
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
