Subject: Re: how to handle dynamic config-file generation?
To: ghen@telenet.be, Geert Hendrickx <geert.hendrickx@ua.ac.be>
From: Julio M. Merino Vidal <jmmv84@gmail.com>
List: tech-pkg
Date: 08/07/2005 14:21:54
On 8/7/05, Geert Hendrickx <geert.hendrickx@ua.ac.be> wrote:
> On Sun, Aug 07, 2005 at 01:51:20PM +0200, Julio M. Merino Vidal wrote:
> > On 8/7/05, Geert Hendrickx <geert.hendrickx@ua.ac.be> wrote:
> > > I'm creating a package for a program which wants to auto-generate its
> > > config file after "make install".  It first checks whether the config=
 file
> > > (in ${PKG_SYSCONFDIR}) exists, and if not, generates a quite generic =
(not
> > > at all host-specific) example config file.  How should I handle this =
in
> > > pkgsrc?
> >
> > Make the package use ${PREFIX}/share/examples/<package>/ instead of
> > ${PKG_SYSCONFDIR}.  This way, the file will never exist and will always
> > be generated from scratch.
> >
> > You can then use the install framework to copy the file into
> > ${PKG_SYSCONFDIR} iff needed.  (See CONF_FILES.)
>=20
> I thought about that, but the package wants to create the file in the sam=
e
> location it expects to find it (PKG_SYSCONFDIR).

Many packages want to do that, and we "fix" them by doing each action
independently (look for the file in one place, but create it somewhere
else).  So it is perfectly correct if you do that.

--=20
Julio M. Merino Vidal <jmmv84@gmail.com>
http://www.livejournal.com/users/jmmv/
The NetBSD Project - http://www.NetBSD.org/