From 98e5ab47c557ff0cec77c897a36f0ba2e4ca8a2c Mon Sep 17 00:00:00 2001 From: spwhitton Date: Sat, 15 Jul 2017 20:59:55 +0000 Subject: convert todo item into a merge request --- .../sbuild_setup_should_use_apt-cacher-ng.mdwn | 23 +++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-) diff --git a/doc/todo/sbuild_setup_should_use_apt-cacher-ng.mdwn b/doc/todo/sbuild_setup_should_use_apt-cacher-ng.mdwn index 450416f2..62f619db 100644 --- a/doc/todo/sbuild_setup_should_use_apt-cacher-ng.mdwn +++ b/doc/todo/sbuild_setup_should_use_apt-cacher-ng.mdwn @@ -1,11 +1,20 @@ -The properties in `Sbuild.hs` should use apt-cacher-ng instead of a bind mount of `/var/cache/apt/archives`. This has at least three advantages: +Please consider merging branch `apt-cacher-ng` of repo `https://git.spwhitton.name/propellor`. -1. more than one instance of sbuild can run at once +Sample text for changelog/description of changes: -2. sbuild can run even if apt is doing something else with its cache - -3. the `piupartsConf` properties are no longer needed. + * Add Apt.proxy property to set a host's apt proxy. + * Add Apt.useLocalCacher property to set up apt-cacher-ng. + * Rework Sbuild properties to use apt proxies/cachers instead of bind-mounting + the host's apt cache. This makes it possible to run more than one build at + a time, and lets sbuild run even if apt's cache is locked by the host's apt. + - If Apt.proxy is set, it is assumed that the proxy does some sort of + caching, and sbuild chroots are set up to use the same proxy. + - If Apt.proxy is not set, we install apt-cacher-ng, and point sbuild + chroots at the local apt cacher. + - Drop Sbuild.piupartsConfFor, Sbuild.piupartsConf, Sbuild.shareAptCache + (API change) + No longer needed now that we are using apt proxies/cachers. + - Update sample config in haddock for Propellor.Property.Sbuild. + Please compare both your config.hs and your ~/.sbuildrc against the haddock. --spwhitton - -[[!tag user/spwhitton]] -- cgit v1.2.3