On Sun, 29 Jan 2006 13:51:29 -0800
Donnie Berkholz <[EMAIL PROTECTED]> wrote:
> And any other "new" file in /etc you also want a USE flag
> introduced for? Sounds real scalable. Or is this just an
> exception from the rule?
Sure it's an exception. I make the difference beetween:
- usual /etc/ files: when they are new, they don't get used before
you start the service or whatever they are owned by. People know
that they should configure things before using them, and that's no
issue. And when they are not new, the changes get CONFIG_PROTECTed,
so there is no issue
- files in some /etc/something.d/: no issue when not new neither,
sure. But when they are new, they affect the existing configuration
of an already in use service with zero protection. It's exactly
like if a pkg_postinst function was doing some "cat new_chunk >>
/etc/something", which i sure you agree would be bad.
Another example of such issues is when i installed laptop-mode
tools for the first time: it messed my acpid configuration, because
it was adding in /etc/acpi/{events,actions}.d some handlers for
things i had already configured differently in my own scripts.
That's that kind of situation i would like to avoid when there are
simple ways to do it, and not any file installation to /etc.
--
TGL
--
gentoo-dev@gentoo.org mailing list
