| 1 |
On Tue, 31 May 2011 10:10:01 +0200, Neil Bothwick wrote about Re: |
| 2 |
[gentoo-user] Cleaning redundant configuration files: |
| 3 |
|
| 4 |
>On Mon, 30 May 2011 23:08:08 +0100, David W Noon wrote: |
| 5 |
> |
| 6 |
>> You have just touched on an annoyance of unmerge, in that it does not |
| 7 |
>> clean up configuration files that have been modified. It removes |
| 8 |
>> files that are still in the same state as when the package was |
| 9 |
>> emerged, but not those modified by the user. I don't see how user |
| 10 |
>> changes make the file more important than would be in its vanilla |
| 11 |
>> state. |
| 12 |
> |
| 13 |
>It doesn't remove *any* files that have been modified, |
| 14 |
|
| 15 |
Erm ... that's what I wrote, above. [That is, of course, predicated on |
| 16 |
the assumption that installing Package A will not modify configuration |
| 17 |
files owned by Package B, and vice-versa: all post-installation |
| 18 |
modifications are performed by the user.] |
| 19 |
|
| 20 |
>the reasons |
| 21 |
>systems used to get cluttered with orphaned .la files. The logic is |
| 22 |
>quite simple, if it is not the file portage installed with the |
| 23 |
>package, it should not be uninstalled with the package. |
| 24 |
|
| 25 |
Why should that be so? If the user has modified a configuration file |
| 26 |
after the previous installation and then unmerges the package, a repeat |
| 27 |
of the configuration changes is all that is required to reinstate it if |
| 28 |
the package is removed in its entirety. The user might even be daring |
| 29 |
and take a backup of the file(s) in question. |
| 30 |
|
| 31 |
To repeat myself: I do not see a customized configuration file as being |
| 32 |
any more important than a vanilla one. If I understand a configuration |
| 33 |
file well enough to customize it once, I remain capable of customizing |
| 34 |
it again after a reinstall. |
| 35 |
|
| 36 |
I should be clear here: a reinstall means "from new, with no previous |
| 37 |
version currently installed" and is quite distinct from an upgrade or |
| 38 |
rebuild. |
| 39 |
|
| 40 |
>There are |
| 41 |
>times when some sort of --force-remove option to remove both these and |
| 42 |
>files in CONFIG_PROTECTed directories would be useful. |
| 43 |
|
| 44 |
Again, what I wrote. |
| 45 |
|
| 46 |
I think we largely agree on this issue. |
| 47 |
-- |
| 48 |
Regards, |
| 49 |
|
| 50 |
Dave [RLU #314465] |
| 51 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
| 52 |
dwnoon@××××××××.com (David W Noon) |
| 53 |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* |
Archives