summaryrefslogtreecommitdiff
path: root/doc/todo/Debootstrap_module_should_respect_a_configured_Apt.proxy/comment_7_571220abc9991ddc940c2cb150543fd2._comment
diff options
context:
space:
mode:
authorspwhitton2017-11-18 17:58:28 +0000
committeradmin2017-11-18 17:58:28 +0000
commit6e8bae97a2e7a25cf73db7c263f92452dc0c2561 (patch)
treebe759d4b739b00820a302ba774a1a5973928a039 /doc/todo/Debootstrap_module_should_respect_a_configured_Apt.proxy/comment_7_571220abc9991ddc940c2cb150543fd2._comment
parent91d0a9524bf6ff3ad5ef4b5f34f903a6fe370d1c (diff)
rename bug/Debootstrap_module_should_respect_a_configured_Apt.proxy.mdwn to todo/Debootstrap_module_should_respect_a_configured_Apt.proxy.mdwn
Diffstat (limited to 'doc/todo/Debootstrap_module_should_respect_a_configured_Apt.proxy/comment_7_571220abc9991ddc940c2cb150543fd2._comment')
-rw-r--r--doc/todo/Debootstrap_module_should_respect_a_configured_Apt.proxy/comment_7_571220abc9991ddc940c2cb150543fd2._comment22
1 files changed, 22 insertions, 0 deletions
diff --git a/doc/todo/Debootstrap_module_should_respect_a_configured_Apt.proxy/comment_7_571220abc9991ddc940c2cb150543fd2._comment b/doc/todo/Debootstrap_module_should_respect_a_configured_Apt.proxy/comment_7_571220abc9991ddc940c2cb150543fd2._comment
new file mode 100644
index 00000000..419b746c
--- /dev/null
+++ b/doc/todo/Debootstrap_module_should_respect_a_configured_Apt.proxy/comment_7_571220abc9991ddc940c2cb150543fd2._comment
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="spwhitton"
+ avatar="http://cdn.libravatar.org/avatar/9c3f08f80e67733fd506c353239569eb"
+ subject="Reassigning this bug to the Chroot and Debootstrap infrastructure"
+ date="2017-11-18T17:57:22Z"
+ content="""
+I'm almost done with my branch, and I now think that this bug applies to the `Chroot` and `Debootstrap` modules. This is how the new sbuild module will work:
+
+ & Apt.useLocalCacher
+ & Sbuild.built Sbuild.UseCcache $ props
+ & osDebian Unstable X86_32
+ & Sbuild.update `period` Weekly 1
+ & Sbuild.useHostProxy
+ & Sbuild.usableBy (User \"spwhitton\")
+ & Schroot.overlaysInTmpfs
+
+As you can see, the propagation of the host's Apt proxy into the chroot is controlled by a property of the chroot, for maximum flexibility. For example, you could replace `Sbuild.useHostProxy` with a call to `Apt.proxy`.
+
+However, the properties of the sbuild chroot will not be applied until after the chroot is built. So, in order to resolve Fred's issue, it is the invocation of debootstrap by the `Chroot`/`Debootstrap` modules that needs to be taught to use the host's Apt proxy, if one is set.
+
+(w.r.t. unpropelling: I'm not going to do any cleanup because /usr/local/propellor is not likely to interfere with the build. What matters is installed build-deps, and we've established there won't be any.)
+"""]]