| 1 |
On Wed, 2006-09-13 at 19:47 +0200, Benno Schulenberg wrote: |
| 2 |
> Ciaran McCreesh wrote: |
| 3 |
> > * If no existing file with the intended target name exists, or if |
| 4 |
> > the existing file has identical content to the file to be |
| 5 |
> > installed, the file to be installed is installed as normal. |
| 6 |
> |
| 7 |
> I would much prefer new files to be treated as if replacing an |
| 8 |
> existing zero length file. When something is installed into /etc, |
| 9 |
> etc-update should alert me to this, because logically speaking a |
| 10 |
> new configuration file is a big configuration change. |
| 11 |
> |
| 12 |
> Ideally the package manager would unconditionally respect the config |
| 13 |
> protection area, and it should be up to tools like etc-update to |
| 14 |
> (configurably) automerge new files and identical files, just like |
| 15 |
> it can be configured to automerge trivial/comment changes. |
| 16 |
> |
| 17 |
|
| 18 |
I disagree. If there is a sane default configuration for something |
| 19 |
(which is most things), I want it installed, so it works out of the box. |
| 20 |
I don't want to have to fiddle with config files to get sshd up and |
| 21 |
running. |
| 22 |
|
| 23 |
Obviously, if there's no sane default configuration (samba?), then the |
| 24 |
installed configuration shouldn't do anything. |
| 25 |
|
| 26 |
Daniel |
Archives