Gentoo Archives: gentoo-dev

From: Drake Wyrm <wyrm@×××××.com>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] CONFIG_PROTECT and unmerging
Date: Wed, 14 Jul 2004 08:10:42
Message-Id: 20040714081159.GC26512@phaenix.haell.com
In Reply to: Re: [gentoo-dev] CONFIG_PROTECT and unmerging by Alan Schmitt
1 At 2004-07-14T09:45:16+0200, Alan Schmitt <alan.schmitt@×××××××××××××.org> wrote:
2 > * Phil Richards (news@××××××××××××××××××××.uk) wrote:
3 > > I raised bug http://bugs.gentoo.org/show_bug.cgi?id=56664
4 > > after a cron job was left behind in /etc/cron.daily following
5 > > an unmerge. I basically agree with the conclusion (WONTFIX)
6 > > but it got me thinking:
7 > >
8 > > Should portage have a "should be deleted" marker for CONFIG_PROTECTed
9 > > files?
10 > >
11 > > It seems odd that there is no indication left behind for
12 > > etc-update (or dispatch-conf) that a config file has been removed.
13 > > These tools could then offer deletion (or even auto-delete if
14 > > the file is known to be the one that got installed).
15 > >
16 > > Is there a show-stopper that makes such functionality a "bad thing"?
17 > > i.e., have I missed something?
18 >
19 > This would be a great feature. I think that Gentoo has a great
20 > configuration management approach (well, better than any other distro
21 > I've tried), but this would make a nice addition.
22
23 The two show-stoppers I can think of:
24 1. Where would we leave that kind of information?
25 2. What happens when multiple packages own a single file?
26
27 I know that point #2 is effectively solved by several devs who rabidly
28 believe that multiple packages owning a single file is a bug, but maybe
29 there's a better way...
30
31 As far as point #1, how about dropping ._meta????_filename files when
32 special actions need to be taken, such as deleting or changing
33 permissions of CONFIG_PROTECTed files.
34
35 --
36 Batou: Hey, Major... You ever hear of "human rights"?
37 Kusanagi: I understand the concept, but I've never seen it in action.
38 --Ghost in the Shell