Bryan Kadzban wrote: > Dan Nicholson wrote: >> 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. > > Automated, no, but this works for me when I update the book to a new > bootscript or udev-config version: > > 1) Export udev-config trunk to a dated directory (in the case of a > release book, it'd be a versioned directory). Tar up this directory. > > 2) Upload the tarball to the downloads area, and get its md5sum. > > 3) Update packages.ent: bump the datestamp and fix the md5sum. > > The critical part is to know that the md5sum will change whenever the > datestamp (or version number) changes, as we just found out. (Seems > kinda obvious in retrospect, but I'm guessing it was the last thing on > Bruce's mind at the time. It didn't help that we didn't document any > requirement for this kind of thing anywhere that I remember.) > > But I think versioning all the releases is a good idea. I.e., instead > of date-stamped versions, call the next tarball of udev-config something > like udev-config-7.0-01.tar.bz2 or something. (Where the 7.0 matches > the intended target book version, and the -01 is a sequential "release" > number for udev-config.) The final 7.0 book could then use the most > recent "release" number: udev-config-7.0-42.tar.bz2, or whatever we're > up to by that point. (Making it use udev-config-7.0.tar.bz2 would cause > this issue again when we release the 7.0 book. So just make it use the > highest "release" number instead.) > > The only problem I see with that might be if we had to do a release for > a book version 6.3.1 or something. (Like if we wanted to collect all > the known errata and run a new stable book or whatever.) But AFAIK we > haven't done a lot of that type of release; none since 6.1.1.
I could do a "stealth" update to 6.3. That is, update what is on the web site without announcements or file name changes. I don't know if that we should do that, but if so, it should be soon. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
