Subject: Re: HEADS UP: RCD_SCRIPTS_EXAMPLEDIR changed to share/examples/rc.d
To: Todd Vierling <>
From: Robert Elz <kre@munnari.OZ.AU>
List: tech-pkg
Date: 12/31/2004 04:25:48
    Date:        Thu, 30 Dec 2004 15:56:03 -0500 (EST)
    From:        Todd Vierling <>
    Message-ID:  <>

  | If the scripts were changed so that the NO (i.e., don't run server) defaults
  | were implied, then what would be *bad* about having all the scripts in a
  | ready-to-go location?

Please, can you attempt to state your end goal here, just what should
happen when a package (daemon type package) is installed, and justify
that.   Without that, we're continuing to miss each other's point.

  | So why isn't the rc.d script put in a ready-to-go place for you, then?

And why isn't it enabled to run as well?   If we're going that one
extra step, why not also take one more.

At the minute things are justifiable by treating the rc.d script an
example that may need to be modified when it is installed - just like
example config files of other kinds - only install those things if
specifically requested.

But, if you're willing to say that all is ready to simply turn on and
run, surely the turn on step should be done as well??

  | Save a step and install it by default to LOCALBASE/etc.  [Provided the
  | ready-to-go directory is configured for use with rcorder,]

Then it can't be LOCALBASE - as rcorder doesn't have the vaguest idea where
that might be (unless you want it reading /etc/mk.conf or something)

  | [*] I should point out that even if you set PKG_RCD_SCRIPTS=YES to override
  |     the NO default when pkg_add'ing, that setting is not saved.

Smells like an oversight, and worth a PR ?