Subject: Re: Config files and packages
To: David Brownlee <abs@formula1.com>
From: Hubert Feyrer <hubert.feyrer@informatik.fh-regensburg.de>
List: tech-pkg
Date: 10/06/2001 01:36:28
On Fri, 5 Oct 2001, David Brownlee wrote:
> What do people think of PLISTs including something like :
> @config <example_config> <live_config>
> eg:
> @config share/examples/analog/analog.cfg etc/analog.cfg
1) Let's not use etc/default, as people may think that's defaults they
can change. Let's stick to the "example thing, i.e. either
share/examples/<pkg> or etc/foo.example (which I'd prefer).
2) We already have something like this in some pkgs:
@exec if [ ! -f %D/etc/pinforc ]; then cp %D/share/examples/pinforc %D/etc/; fi
If you want to replace this with
@config pinforc etc/pinforc
That's fine with me, but only syntactical sugar. We could even do
a simple substitute from bsd.pkg.mk without changing pkg_*.
If so, I recomment we use @CONFIG to make a visual difference from
@-macros built into the pkg_* tools vs. the one(s) in bsd.pkg.mk
3) What do you suggest for deinstallation? Unchanged config files should
not be left back IMHO, so something like
@unexec if ! cmp -s <orig> <config>; then rm <config; fi
might be in place. It can also simply be added from bsd.pkg.mk
(check the place where we add @exec/@unexec commands for info files :)
- Hubert
--
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
* Setup -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org/