Martin Michlmayr <[EMAIL PROTECTED]> writes: > The problem of running multiple sbuild instances at the same time in > different chroots is that they all have their own > chroot-*/var/cache/apt/archives directory in which downloads are put. > It would be nice if all instances would share one cache. > > Now I realize that this is only possible in split mode and not when > using schroot and that you could argue that I should simply use a > proxy, but maybe it would at least be possible to add something to the > documentation, e.g. an example of how to bind mount the > /var/cache/apt/archives dir and how to achieve it with sbuild. > > I suppose my situation is not very common since I'm building the same > suite with multiple sbuild instances. Sharing the cache dir probably > wouldn't help much if you built different suites. However, it > certainly cannot hurt... > > Another important factor is disk space saving.
I was advised (IIRC by dato or vorlon) that this wasn't a good idea,
due to the shared locks, which can cause builds to fail waiting on the
APT cache lock. They recommended using a webcache such as SQUID to
cache the downloads transparently, or running a local mirror.
We can certainly document it, but I'm not convinced this is something
we should be recommending to our users.
Regards,
Roger
--
Roger Leigh
Printing on GNU/Linux? http://gutenprint.sourceforge.net/
Debian GNU/Linux http://www.debian.org/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
pgptxKhq5DqWB.pgp
Description: PGP signature
