1 |
On Thu, Feb 05, 2004 at 10:48:35AM +0100, in <200402051048.36660.pauldv@g.o>, Paul de Vrieze <pauldv@g.o> wrote: |
2 |
> On Thursday 05 February 2004 09:13, Drake Wyrm wrote: |
3 |
> > I have to disagree completely. This is exactly why we use |
4 |
> > CONFIG_PROTECT and etc-update. Packages *should* install a default, |
5 |
> > but it shouldn't be called <config-file>.example. Documentation, such |
6 |
> > as a config file example, belongs in /usr/share/doc/<package>. When |
7 |
> > you re-emerge something, it should try to install everything it needs. |
8 |
> > If the destination file is in a CONFIG_PROTECT directory, Portage does |
9 |
> > exactly what you described (with a .cfg-XXXXX- prefix rather than an |
10 |
> > .example suffix). |
11 |
> > |
12 |
> > With regard to default config files: look at </etc/mutt/Muttrc>. |
13 |
> > Emerge net-mail/mutt, if you must. Beautiful example of the Right |
14 |
> > Way(tm) to write a default. |
15 |
> |
16 |
> Basically muttrc is not of the same class as passwd, fstab and group. If |
17 |
> you're up to it, just move the three to somewhere else and reboot. After |
18 |
> that I think you can appreciate that one must not be enabled to |
19 |
> overwrite them. |
20 |
|
21 |
Ummm... Pass. Might be something I try right before the next time I get |
22 |
the urge to wipe everything and reinstall from scratch. Falls in the |
23 |
same category as trying `rm -rf /`. Only need to do it once, but you |
24 |
gotta do it. |
25 |
|
26 |
> First the defaults for those files can not and will not give you a |
27 |
> working setup. Basically when these files exist, the only way to create |
28 |
> usable new ones is to base them of the existing ones. These files are |
29 |
> system specific and cannot have reasonable defaults. |
30 |
|
31 |
I give you half credit. `proc /proc proc defaults 0 0` and `tmpfs /dev/shm |
32 |
tmpfs defaults 0 0` are examples of reasonable defaults. Furthermore, |
33 |
where reasonable defaults cannot be assumed, reasonable comments can be |
34 |
used. *That* is what I specifically like about the default Muttrc. |
35 |
|
36 |
> It is never ever a |
37 |
> good idea to overwrite the current version with the config-protected |
38 |
> one. The only alternative solution I see would be to patch etc-update to |
39 |
> automatically ignore/remove these updates. |
40 |
|
41 |
I have another alternative for you: don't overwrite your configs. |
42 |
|
43 |
Seriously, though, the real blocker here is that *sometimes* we |
44 |
*need* to make a distro-wide change to something like fstab. The |
45 |
config-protect/etc-update mechanism is currently the only method we have |
46 |
of distributing these changes without breaking users systems. |
47 |
|
48 |
If you really want to do something like what you're describing, I imagine |
49 |
it wouldn't be too hard to write a script to do that for you. Something |
50 |
involving `find ${CONFIG_PROTECT} -path /etc/.cfg-????-fstab -o -path |
51 |
${another-uberprotected-file} -exec rm '{}' ';'` Post it when you |
52 |
finish. There are probably others who will get some use from it. As for |
53 |
myself, I will make those decisions personally. |
54 |
|
55 |
-- |
56 |
Batou: Hey, Major... You ever hear of "human rights"? |
57 |
Kusanagi: I understand the concept, but I've never seen it in action. |
58 |
--Ghost in the Shell |