Re: forced sysconfdir in net/bind*

["Johnny C. Lam" <jlam%NetBSD.org@localhost>]

On Tue, Feb 14, 2017 at 09:59:27AM -0600, J. Lewis Muir wrote:
> On 02/14, Johnny C. Lam wrote:
> > On Mon, Feb 13, 2017 at 11:34:06AM +0100, Filip Hajny wrote:
> > > 
> > > since a commit in 2000, all net/bind* packages have hardcoded /etc for
> > > sysconfdir. I can only assume this was done for the benefit of the
> > > platform /etc/named.conf file that pre-exists on NetBSD. This makes
> > > things confusing on other platforms though that do not come with such
> > > and do not use /etc for PKG_SYSCONFBASE (and the package doesn?t
> > > generate its own by upstream decision).
> > > 
> > > I?d like to change the packages to use a standard $PKG_SYSCONF layout,
> > > but maybe I?m missing something. Is it worth leaving the existing rule
> > > in place conditioned for NetBSD only?
> > 
> > (I removed pkgsrc-users@ so as not to cross-post.)
> > 
> > Yes, change it to match how the rest of pkgsrc works.  No, it's
> > not necessary to keep some special setting for NetBSD because there
> > shouldn't be anything special about the sysconfdir setup for NetBSD
> > as opposed to other platforms.  Just make your change for all of
> > the bind packages and bump the PKGREVISIONs.
> 
> Also note that there is another pkgsrc package that has special
> behavior: shells/standalone-tcsh.  It installs with PREFIX=/ regardless
> of what PREFIX is actually set to.  See [1] and [2] for comments on
> that.

I see two approaches to this issue.

1. Turn standalone- and static- into PKG_OPTIONS for shells/tcsh.  This
   allows adding PKG_OPTIONS+=tcsh-standalone to your /etc/mk.conf to
   build your own standalone tcsh, and it preserves the normal
   expectation of pkgsrc installing into ${LOCALBASE} by default.  This
   loses a bulk-built package because "tcsh-standalone" would not be a
   default option.

2. Create a "standalone" category to house these variants of the main
   packages that will install into / instead of ${LOCALBASE}.  A
   separate category makes it apparent that those packages will all
   break the expectation of pkgsrc installing into ${LOCALBASE} by
   default.  This separate category can still be bulk-built.

-- Johnny C. Lam