Subject: Re: post-installation and rc.d enhancements
To: None <email@example.com>
From: Julio Merino <firstname.lastname@example.org>
Date: 04/17/2002 18:58:18
Content-Type: text/plain; charset=us-ascii
On Wed, Apr 17, 2002 at 09:51:36AM -0500, Frederick Bruckman wrote:
> On Thu, 18 Apr 2002, Luke Mewburn wrote:
> I like that a lot (and the rest). I have one question...
Me too :)
> I guess the idea is that the package system just creates that file (with
> suitable defaults) if and only if it doesn't already exist. That breaks
> down if the file ever needs to change. Alternatively, I think the number
> of pkg_ rc.d scripts will be small enough, that we could probably craft
> a single defaults/rc.pkg.conf file and include the latest version in
> every binary package which has an rc.d script. ["/etc/rc.conf.d/$name"
> loads after "/etc/rc.conf" in load_rc_config(), so editing the former
> would still be an option.]
The /etc/defaults/rc.pkg.conf would be modified by installation scripts,
I guess. That is, when a package that needs some rc.d script is installed,
it will modify the rc.pkg.conf defaults to add its own list of variables.
If any of them is already found, just overwrite them to match the new
needs. /etc/rc.conf.d/* should be left for the user...
Of course it runs NetBSD - http://www.netbsd.org
HispaBSD member - http://www.hispabsd.org
Julio Merino <email@example.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org
-----END PGP SIGNATURE-----