Le jeudi, 16 juin 2011 09.21:10, Alex Hermann a écrit : > On Wednesday 15 June 2011 23:37:15 Josua Dietze wrote: > > O.K., so let's assume a user puts a changed/added config file into > > /etc/usb_modeswitch.d. It is preferred over the files in the package. > > One day there is a package update, and the new/changed configuration now > > comes included with the new package, probably improved over the "manual" > > file or with new parameters. What should happen then? > > There are more software packages using this scheme (udev, mysql, pam) > although most place all configs in /etc. I have no idea about the amount > of support/bugreports this causes. IMHO, if a user changes/overrides the > config he is responsible for tracking changes to the default config. > Packaging scripts warning about them may help though.
I agree with Alex here, although the "warning" bit is tricky to do correctly. The easiest path of action is to have usb_modeswitch loudly warn the administrator using overrides (new or changed, e.g. trough syslog), mentioning that any override should get included in the official tarball (I can consider removing the bug presubj [which currently recommends to go to the upstream forum] of usb-modeswitch-data to have such bugreports tracked in the Debian BTS). IMHO the constant goal is to have zero overrides around: I mostly see the override mechanism as an easy way to work new config files out. > If new/updated configs are shipped by upstream timely, it will only be a > few 'early adopters' having the need to override configs reducing the risk > of support needed by users who 'forgot' about their overrides. An other thing to consider is that a working override is not supposed to "stop working" after usb-modeswitch upgrades: if usb-modeswitch keeps some backwards compatibility, at worse, the override config file will work sub-optimally. Cheers, OdyX -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
