| 1 |
On Thu, 9 Oct 2003 12:59:17 +0200 |
| 2 |
Paul de Vrieze <pauldv@g.o> wrote: |
| 3 |
|
| 4 |
> |
| 5 |
> Is this really necessary? It would go against the principles of well |
| 6 |
> design. Not editing a configuration file should not break a system. In |
| 7 |
> any case, make sure that this configuration that must be removed, can |
| 8 |
> only be added by the user manually. If you merge a package and |
| 9 |
> immediately ummerge that package, the state of the system should be |
| 10 |
> unchanged. |
| 11 |
> |
| 12 |
|
| 13 |
Well in theory i agree with you, but any package that installs files to |
| 14 |
a CONFIG_PROTECT dir will not leave the system changed after the |
| 15 |
unmerge. |
| 16 |
The problem in the particular case i am working is a bit complicated |
| 17 |
because it is a "module" for a package already installed. And to make |
| 18 |
the "module" work after installing one has to edit a config file. And |
| 19 |
altought removing the module will not break the main package it would be |
| 20 |
cleaner to edit the configuration file and remove the module references. |
| 21 |
|
| 22 |
-- |
| 23 |
Gustavo Felisberto |
| 24 |
(HumpBack) |
| 25 |
------------ |
| 26 |
It's most certainly GNU/Linux, not Linux. Read more at |
| 27 |
http://www.gnu.org/gnu/why-gnu-linux.html . |
| 28 |
------------- |
Archives