On 8/29/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote: > > In the future, I'll need to figure out how to copy the proper config > files from the development bz2 files instead of regenerating them.
I've thought about this a bunch of times, but I can't really think of an ideal way to make this automated. Some possibilities: 1. Always generate the tarball manually so that you can make the appropriate updates in the book packages.ent file before the render step. The render script would just have to output a strong reminder to do this or something. The drawback is extra work and more failure points. 2. Always use the dated tarball and just copy it instead of generating it. The drawback is that there isn't a clear correlation between LFS release and the data files. 3. Decouple the data projects from the LFS book. I.e., make lfs-bootscripts a fully versioned project. This is the same as 2, but with real versions instead of snapshot dates, e.g. lfs-bootscripts-0.1.2. The drawback being that the projects might have to be split up for version controlling reasons (tags and branches of the book wouldn't necessarily correspond to tags and branches of the data files). I think 1 is probably the easiest to do right now, even though it adds an extra step. It's also nice to have a clear correspondence that "this set of udev rules works with what's in this LFS version". -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
