Stephan Seitz wrote: > Every package which will accept a configuration file in /etc should ship > such a file in /etc, even if it contains only comments. In this way, you > know the name(s) of the configuration file(s) and the subdirectory in > /etc where they belong.
A de-facto standard has already emerged for how to ship the standard configuration in /usr/lib and handle overrides, which makes it quite straightforward to find configuration files in a package, add new configuration files, or override the standard configuration files: packages read /etc/$dir before /usr/lib/$dir, and /etc/$dir/$foo.conf overrides /usr/lib/$dir/$foo.conf. If you want to override /usr/lib/$dir/$foo.conf, copy it to /etc/$dir/$foo.conf and start editing. - Josh Triplett -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111230150916.GA8957@leaf
