Dan Nicholson wrote: > On 1/22/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote: >> Dan Nicholson wrote: >>> One thought is to put them in the patches repo. Another thought is to >>> make a xorg-modular directory in the BLFS repo and change the render >>> script to copy these to some standard location. Another possibility is >>> to take a similar process that LFS has with udev-config where the >>> files live in the LFS repo, but it's up to the editor to put the >>> updated files in the right download location (anduin in this case). >> I'm not sure how many files you have in mind or where you want to >> download them from. That said, I don't see any reason to not just put a >> file of md5sums into the book's svn and then set up a cron job to check >> for updates on anduin once a day. > > It's like 6 files. There's one huge md5sums file that has all the > md5sums for all the modular packages. Then there are wget lists for > each of the sections: proto, util, app, data, font and driver. OK, 7 > files. Whatever you think is the best way to get from SVN to > downloadable file, you have a lot more experience there.
OK. Lets create a new directory under svn's trunk called auxfiles: trunk/auxfiles/ and put the files there. After the files are in svn, I'll just do a 'svn co svn://svn.linuxfromscratch.org/BLFS/trunk/auxfiles' And then can just do an update periodically from cron with a 'svn update' from the files/BLFS/ directory.. We can access them from http://anduin.linuxfromscratch.org/files/BLFS/auxfiles/ Does that sound OK? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
