On Mon, Mar 21, 2011 at 12:02:21PM +0100, Antoine Jacoutot wrote:
> On Mon, 21 Mar 2011, Marc Espie wrote:
>
> > On Sun, Mar 20, 2011 at 08:36:35PM -0400, Brad wrote:
> > > >It will solve things, but we have to design/document SYSCONFDIR
> > > >completely.
> > > >I vote for it to be readonly and not changed by users anywhere...
> > > >There might be need for a port-dependent config dir that would be derived
> > > >from SYSCONFDIR.
> > > >
> > > >How to name it ?
> > >
> > > It would make more sense to have a variable name such as CONFDIR and
> > > set it to /etc which is then readonly. Allow SYSCONFDIR to be
> > > overridden as it is now for ports that want the config files in a
> > > subdir of CONFDIR.
> > >
> > > CONFDIR= /etc
> > > SYSCONFDIR?= ${CONFDIR}
> > >
> > > .e.g. for net/powerdns
> > >
> > > SYSCONFDIR= ${CONFDIR}/pdns
> > >
> > > Since you want --sysconfdir passed to autoconf anyway and it already
> > > is. This makes it simpler and cleaner.
> >
> > Yes, I think this is the most reasonable approach.
> >
> > Anyone disagree with those names ?
>
> Not really. The only thing that I can say is that I've seen some
> software using CONFDIR in their Makefiles that would point to something
> like /etc/prognam/ . I have no idea whether that is a problem or not.
> What I'm trying to say is that CONFDIR may be a bit too 'generic'.
BASESYSCONFDIR ?
