>>>>> mictlan tecutli <[email protected]> writes:
>> k is that the lh_config creates the config/ directory, but when I
>> run lh_build it creates a new chroot/ directory and caches the
>> packages there. So do I need to point to the existing cache before
>> running the lh_build command? Any suggestions gratefully accepted!
> you can use apt-cache, approx or any other proxy that caches the
> debs.
I guess that a general purpose caching proxy, such as Squid, may
help as well. (And Squid is a nice thing when there's slow
Internet connection, anyway.)
> you can copy the debs that you already have to the cache.
Or, the packages could be moved to some place, and then replaced
with symlinks, like:
# yes n | mv -vi -- .../*.deb /var/cache/apt/archives/
# yes n | ln -is -- /var/cache/apt/archives/*.deb .../
This will help saving not only the bandwidth, but the disk space
as well.
> and the you tell live helper to use the url of the cache to download
> packages, instead of the default, ala:
> lh_config -m http://localhost:9999/debian --mirror-chroot-security
> http://localhost:9999/security
--
FSF associate member #7257
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
