policy for application specific config files?

[Steffen Sledz <sledz@dresearch.de>]

Is there a policy to handle application specific config files?

Let's say we've this situation: A service (let's say rsyslog)
is started with a parameter telling it the config file to use.
The name of the config file can be set using a variable CONFFILE
in file /etc/default/rsyslog which can be overwritten for distros
or machines easy.

But i like to use specific config files for different applications
(represented by extra recipes/packages).

A solution could be to modify /etc/default/rsyslog in a way that
it looks for other files existing in e.g. /etc/rsyslog.d and
sourcing them all after it's own code. So the other packages can
install files into this dir allowing to redefine CONFFILE without
interfering with the files from rsyslog package.

Is this the way it goes?

Regards,
Steffen