On Wednesday 15 June 2011 23:37:15 Josua Dietze wrote: > Am 15.06.2011 21:56, schrieb Alex Hermann: > > An override config file should have higher priority than shipped config > > of course. > > 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. 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. -- Alex Hermann -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
