On 2/3/07, Bryan Kadzban <[EMAIL PROTECTED]> wrote: > > Looking at my shell history, it looks like when I made a udev-config > tarball, I did an svn export, then renamed the directory to have the > datestamp in its name, then tar/bzip2ed it, then grabbed an md5sum and > updated the filename/md5sum in the book. Then, I scp'ed it to belg, did > a "chgrp wwwdownloads", and moved it to the downloads.lfs.org vhost > directory. Hopefully that's sufficient for the bootscripts.
Right, I asked Bruce to do it this way since the old way of generating the tarball left you in a position of not knowing the md5sum till after the render. The way it is now, any of the editors can commit away on udev-config or bootscripts. When they're ready, they generate a tarball just like Bryan explained above for downloads.lfs.org. This gives two bonuses in my mind: 1. A new tarball isn't created every time you make a commit. The editor controls when things are stable enough to roll a new version. 2. You create the tarball, so you know all the stats and can enter them in the book. This will invariably come out different in a script since the tarball has to contain info on all the dates/perms/ownership. -- Dan -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
