Randy McMurchy wrote:
LFS releases a book, perhaps in print, that says this is the bootscript
tarball for this release. Let's call it bootscripts-1.2.3. This has
LFS and BLFS scripts in it.
Before BLFS releases their book to match the new LFS version, it is
discovered that some of the bootscripts needed to be touched up, or
a new one needs to be added.
How does LFS update their finished, released, perhaps in print, book
to reflect that a new tarball is needed?
Obviously we can't. I think BLFS should handle this as with any other
upstream package bug. You either patch it to address the issue, or you
use a newer version available from upstream (with subversion's branching
capabilities it's trivial for the bootscripts/udev/whatever team to
ensure that the versions in LFS and BLFS differ *only* in the way(s) you
want/need it to).
Regards,
Matt.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
