Gentoo Archives: gentoo-user

From: Dale <rdalek1967@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Cleaning redundant configuration files
Date: Wed, 01 Jun 2011 18:08:18
Message-Id: 4DE67F9F.8060402@gmail.com
In Reply to: Re: [gentoo-user] Cleaning redundant configuration files by David W Noon
1 David W Noon wrote:
2 > On Wed, 01 Jun 2011 18:20:02 +0200, Neil Bothwick wrote about Re:
3 > [gentoo-user] Cleaning redundant configuration files:
4 >
5 >
6 >> On Wed, 1 Jun 2011 15:57:58 +0100, David W Noon wrote:
7 >>
8 > [snip]
9 >
10 >>> Remember: we are discussing the COMPLETE DELETION of a
11 >>> package, not an upgrade or rebuild.
12 >>>
13 >> We are discussing unmerge behaviour, unmerging is part of the upgrade
14 >> and rebuild processes.
15 >>
16 > Now I see why we are talking/writing at cross purposes.
17 >
18 > What I am proposing I would apply only to -C or -c options on an emerge
19 > command, not the internal actions during an upgrade/rebuild. I have
20 > stated that several times in this thread, so I thought I had made
21 > myself clear.
22 >
23
24 Even if the -C option is used, I would still want it to be something
25 extra to remove config files. As stated before, I sometimes emerge -C a
26 package then emerge it again. I still want the config files to be left
27 alone tho. I have also had to do this before for *B*lockers where
28 portage couldn't do it itself for whatever reason.
29
30 I would think this would be a idea on this. Do a emerge -C to get the
31 regular way and a emerge -CC to remove everything literally, including
32 config files.
33
34 As someone else posted, I seriously doubt the devs will do this.
35 Possible but not likely. I like the idea but still want it to be
36 something extra to get it and not the default for sure.
37
38 Dale
39
40 :-) :-)

Replies

Subject Author
Re: [gentoo-user] Cleaning redundant configuration files Neil Bothwick <neil@××××××××××.uk>