Subject: Re: ssh [was: Re: CVS commit: basesrc]
To: None <hubert.feyrer@informatik.fh-regensburg.de>
From: Luke Mewburn <lukem@cs.rmit.edu.au>
List: tech-pkg
Date: 03/16/2000 01:18:42
Hubert Feyrer writes:
> On Thu, 16 Mar 2000, Luke Mewburn wrote:
> > I don't exactly have the time to search through the hundreds (?)
> > thousands (?) of packages looking for which ones have rc scripts.
> > 
> > Maybe if someone provided a list I could work with them on writing
> > `new world order rc.d' scripts for the packages...
> 
> yui# cd /usr/pkgsrc/
> yui# grep rc.d */*/pkg/PLIST*
> [ ... ] 
> 
> More than I expected...
> 
> Please: can we agree to not rewrite the existing scripts 100% to use all
> the new mag^Wfeatures available, but just change them enough to use
> everything that's needed. Else the programs' maintainers are unlikely to
> take back our changes, and we'll have to maintain things on our own, which
> our present manpower does not really allow.


I really don't care if the scripts use the rc.subr functions or not.

However, some guidelines should be followed:
	* the scripts should support at least
		start stop
	* the scripts probably should support (if appropriate)
		restart reload status
	* the scripts should be installed +x
	* the scripts shouldn't end in `.sh' once installed because
	  that indicates to run_rc_script that the script should be
	  sourced into the current environment rather than run in a
	  subshell. Very few scripts need to run in the current
	  environment (e.g, fsck.sh does because it might need to exit
	  and stop the boot process)

I'm sure I'll think of other guidelines when I hopefully get a chance to
write up the documentation later this week.