Subject: Re: rc.d scripts recorded in PLIST (was: CVS commit: pkgsrc/mk)
To: Jeremy C. Reed <firstname.lastname@example.org>
From: Greg A. Woods <email@example.com>
Date: 09/11/2003 13:51:19
[ On Thursday, September 11, 2003 at 01:12:23 (-0700), Jeremy C. Reed wrote: ]
> Subject: rc.d scripts recorded in PLIST (was: CVS commit: pkgsrc/mk)
> On Sat, 6 Sep 2003, Johnny C. Lam wrote:
> > Modified Files:
> > pkgsrc/mk: bsd.pkg.install.mk
> > Log Message:
> > Install the rcd scripts at post-install time, not at post-install-script
> > time. The rc.d script needs to be recorded in the PLIST, and
> > post-install-script time is too late if we use dynamic PLISTs.
It does, but that's the wrong way to do it.
> If I understand this correctly, does this mean that we will soon be able
> to remove rc.d/ script references from PLISTs, because they will be
> automatically recorded?
> (If so, that is good; and I was already doing that myself on a few systems
Actually, no, it's not good at all.
The rc.d script is not really a part of the package -- it's a
configuration file. At least that's been the apparent consensus.
Remember? It's supposed to be installed in share/examples/rc.d and then
copied into /etc/rc.d only if the admin wants to auto-enable the package!
The rc.d script can only be removed at de-install time IFF the admin
wants it removed at that time! Automated de-install actions must never
assume they can un-do manually done operations!
> That would be like the autoregistration of etc/ configs in PLISTs.
Indeed it would, which is part of the problem! The pkgdb +CONTENTS
files don't yet have any way to denote configuration files separate from
example configs, or other "non-modifiable" files.
Johnny needs to re-think this change -- I think he's made a grave
mistake, and as far as I can see he's still ignored all the calls to
have rc.d scripts properly installed and registered in share/examples/rc.d
I still have, and use daily, patches that do exactly that.....
Greg A. Woods
+1 416 218-0098 VE3TCP RoboHack <firstname.lastname@example.org>
Planix, Inc. <email@example.com> Secrets of the Weird <firstname.lastname@example.org>