On Tue, Mar 25, 2008 at 4:48 AM, <[EMAIL PROTECTED]> wrote: > I just don't know very much about lh yet to comment, but a more > "central" package cache/repository might make sense (especially when > building several variants of live images). It should be simple enough to > survive version changes of the lh machinery (and accomodate different > repositories). What do you think? You may be interested in apt-cacher; install and configure it, then use lh_config --mirror-chroot http://127.0.0.1:3142/ftp.debian.org/debian/ \ --mirror-chroot-security "http://127.0.0.1:3142/security.debian.org/"; \ --foo --bar --baz The packages will download from the internet once, and henceforth use the cached versions. When new versions come out, they'll properly be fetched once and cached. The total cost of building several times is greatly reduced, and you can also set up your "real live" apt to use it as well. This is a convenient setup if you have several machines on your network running Debian, as well; they can all point to the same machine for their cache and reduce the time to update them. I use this method, and achieve several megabytes per second download while building debian live.
Apt-cacher is a bit buggy, it seems; occasionally you'll get "method http died unexpectedly" or a download will stall halfway. At that point, further attempts to download this package will continue to fail; remove the /var/cache/apt-cacher/packages/foo.deb file, it will re-download from the Internet and things will once again be happy. All in all it's less trouble than it sounds like. Will _______________________________________________ debian-live-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-live-devel
