Sune Vuorela found this quote from etch_rc_policy: Packages must not modify other packages' configuration files except by an agreed upon APIs (eg, a /usr/sbin/update-foo command).
At the first sight this makes the trivial implementation a policy violation. However after much discussion on #debian-release, I got this from vorlon: [...] [2007-03-11 23:00] <cheal> wait, that's the same thing [2007-03-11 23:01] <cheal> managing X config vs modifying a configuration file. I'm afraid I may be tired but I don't get the difference [2007-03-11 23:01] <vorlon> the difference is that it's not a *package* modifying config files [2007-03-11 23:01] <vorlon> its a *user* modifying config files [2007-03-11 23:01] <vorlon> by invoking a config file management tool [2007-03-11 23:04] <cheal> vorlon: hum. in that case do you agree that ksynaptics can be considered a config file management tool? [2007-03-11 23:07] <vorlon> ... [2007-03-11 23:07] <vorlon> no So "package" must be red with care. Whether the trivial implementation would violate policy depends on whether ksynaptics is considered a config file management tool. I think it can be considered one, but vorlon thinks the opposite. Mark, if you're tempted to implement the trivial implementation, I suggest discussing first with vorlon or on debian-devel whether ksynaptics is a configuration file management tool. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
