From fc2a19bbd8366ff208e1cce2e9891601a435eb96 Mon Sep 17 00:00:00 2001 From: spwhitton Date: Sat, 2 Sep 2017 02:58:06 +0000 Subject: add link --- doc/todo/unpropelling_a_host.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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.. -- cgit v1.2.3