summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorspwhitton2017-09-02 02:58:06 +0000
committeradmin2017-09-02 02:58:06 +0000
commitfc2a19bbd8366ff208e1cce2e9891601a435eb96 (patch)
tree49c1c96243dac537a9237e72151871df7b1bb484
parent2c41836bd7eb0695ff0cfc49f0bc8e4a7266e7b0 (diff)
add link
-rw-r--r--doc/todo/unpropelling_a_host.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/todo/unpropelling_a_host.mdwn b/doc/todo/unpropelling_a_host.mdwn
index 0e1ee2b5..5c31bd90 100644
--- a/doc/todo/unpropelling_a_host.mdwn
+++ b/doc/todo/unpropelling_a_host.mdwn
@@ -2,7 +2,7 @@ We discussed at DebConf the need for a property that removes propellor from a ho
1. There is no standard way to remove cabal and stack packages from `/root` without potentially nuking stuff the user wants to keep. So maybe the property should remove only OS packages? I.e. best used on `OSOnly` hosts/chroots.
-2. What if another property on the host installs some or all of those build dependencies? This property would be cancelled out by the unpropellor property. Maybe properties that install packages need to set info about the packages that are meant to remain installed?
+2. What if another property on the host installs some or all of those build dependencies? This property would be cancelled out by the unpropellor property. Maybe properties that install packages need to [[set info about the packages that are meant to remain installed|todo/metapackage]]?
The unpropellor property could just nuke `/usr/local/propellor` and leave it at that. But then the sbuild module would need to maintain a list of propellor's build deps to remove from the newly created chroot, which is a third copy of the list..