Subject: Re: PLIST content
To: None <firstname.lastname@example.org>
From: Hubert Feyrer <email@example.com>
Date: 07/02/2006 23:13:18
On Sun, 2 Jul 2006 firstname.lastname@example.org wrote:
> As I tried to explain in reply to Roland, I'd like to handle the
> situation of mmodular configuration files as much as possible. Many
> daemons and other programs have some kind of include mechanism which
> allows splitting large configuration files into smaller pieces. When we
> want to be able to gracefully handle configuration files, we need to be
> able to deal with it, so that they can all be archived / deleted in
> unison. Requiering them to be kept in the subtree is a good compromise
> which reflects what most users do anyway.
> One target audience is automatic deploiment. E.g. for a DNS server two
> components are needed: the binary package and the configuration archive.
> When I can allow this with generic frontends on top of pkg_add, I gain
> some useful functionality, IMO.
While there: it would be nice if we had some solution for config files for
packages that do _not_ have any way to include things - I'm thinking of
the tex-bigtex and tex-jadetex packages, which both need adding a few
lines to some .ini file.