----- Original Message -----
> I'm back considering this change ...
>
> OPTION A
>
> Introduce $PCP_SYSCONF_DIR to expose $sysconfdir via pcp.conf
> and then move everything currently below
> $PCP_VAR_DIR/config/<foo> to
> $PCP_SYSCONF_DIR/<foo>.
>
> and ...
>
> On Sun, 2012-11-25 at 17:06 -0500, Frank Ch. Eigler wrote:
>
> > One tricky aspect could require some packaging scripting, that
> > being
> > the migration of config files from the old to the new locations.
>
> I have two questions for the gallery ...
>
> 1. Should the default setting for $PCP_SYSCONF_DIR be /etc or
> /etc/pcp.
> The former would lead to a bunch of dirs in /etc,
> e.g. /etc/pmcd, /etc/pmlogger, /etc/pmie ... The latter would
> aggregate
> all the PCP config files below /etc/pcp, so we'd have directories
> like /etc/pcp/pmcd, /etc/pcp/pmlogger, /etc/pcp/pmie ...
>
> I prefer collecting all these directories below /etc/pcp and
> minimizing
> the name pollution (and possible collisions) in /etc.
>
Sounds good to me. FWIW, Debian policy docs state:
(http://www.debian.org/doc/debian-policy/ch-files.html)
10.7.2 Location
Any configuration files created or used by your package must reside in /etc. If
there are several, consider creating a subdirectory of /etc named after your
package.
If your package creates or uses configuration files outside of /etc, and it is
not feasible to modify the package to use /etc directly, put the files in /etc
and create symbolic links to those files from the location that the package
requires.
So, /etc/pcp/* sounds fine to me, and we don't need to go for
symlinks since we can set the direction to wherever we like.
I guess you might consider symlinks from the old location to
the new if you're concerned about fallout from a move (rather
than removing the old path entirely). But personally I think
a clean cutover is best for the long-term.
cheers.
--
Nathan
|