On 5/26/06, DJ Lucas <[EMAIL PROTECTED]> wrote:
I am fine with merging the bootscripts if the community wants it. That is conditional on the ability to create an auto generated tarball (not a big deal). Also, the editors must have access to their respective directories under the bootscripts repo (same as the requirements for udev). Again, IIRC, it was not a big deal to make the post commit hook on the BLFS book's changed tarball date. I haven't seen the existing one, but an anonymous co and export (don't go mucking around in the repo directly) on belgarath each time the bootscripts date changes seems it'd work well. Syncing them between the books for a single tarball is where it would be difficult. Actually, even that shouldn't be bad. Only generate the tarball if it's not already there. I'm not sure, off the top of my head, how to handle changing the bootscripts date in the other two books. Now, when this was mentioned to me previously, I did not know that this included BLFS's scripts. This can present a problem for release cycle, unless we can be *very* sure that BLFS will not need to add another bootscript after LFS reaches release. Generating the official book tarball can be added to the LFS release checklist to minimize this possibility. The same goes for CLFS scripts, though they'll change less frequently. The scripts for CLFS are lfs-bootscripts + CLFS additions for additional hardware. As it is right now, changes that go into LFS must be duplicated in CLFS's repo, or a patchset kept current (and potentially the reverse). To me, that merge is a no-brainer.
"Those who ignore history are bound to repeat it". Once upon a time LFS and BLFS bootscripts used to be part of the same package. They were split up for the reasons mentioned above. Unless LFS and dependent projects commit to coordinate their release cycles, having a common tarball for anything (and that includes udev rules) will be a problem. IMO, the best solution is the one suggested by Matt. LFS should contain the udev rules and bootscripts for LFS. All dependent projects should work off that base and release their own additions (or deletions in form of patches) - similar to how the bootscripts are currently handled. -- Tushar Teredesai mailto:[EMAIL PROTECTED] http://www.linuxfromscratch.org/~tushar/
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
