Subject: Re: pkg/7322
To: None <email@example.com>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 04/05/1999 09:15:14
[ On , April 5, 1999 at 00:41:48 (-0000), email@example.com wrote: ]
> Subject: Re: pkg/7322
> I'm looking into your package right now and have two questions:
> - why would you want to generate the rc.d/snmpd.sh script on every
> installation of the package instead of shipping it with the package?
> Creating and deleting it will ensure that for any package upgrades, the right
> right script will be in place, instead of one remaining from an old versino
That's just the way it worked before -- I was just being lazy and all I
did was move the existing code from the makefile to the INSTALL script.
In theory the script template could be shipped in the files subdirectory
and then have it transformed and installed in the share/examples
directory by the Makefile and copied to .../etc/rc.d by the PLIST if one
doesn't already exist.
It is quite possible that the script could be used for all of the
daemons in the package as well as any other things that one might want
to do in a startup script (such as generate an SNMP trap too), so if you
consider there to be a one-to-one relationship with startup scripts and
packages then the script can't be installed directly into .../etc/rc.d
because it is likely to be edited locally.
> - I've added a dlmod/.keepme file to keep that directory in case something really
> happens to dig out a dlmod.
OK. I don't really understand yet why no modules were built in this
version, but I was just as happy there weren't any after I discovered
that the only easy way to trick it into using libwrap was to link the
entire thing statically (and thus totally avoid our little dyanmic
Greg A. Woods
+1 416 218-0098 VE3TCP <firstname.lastname@example.org> <robohack!woods>
Planix, Inc. <email@example.com>; Secrets of the Weird <firstname.lastname@example.org>