Subject: Re: Startup scripts (patch proposal)
To: None <>
From: Julio Merino <>
List: tech-pkg
Date: 05/23/2002 16:37:10
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, May 23, 2002 at 08:25:52AM -0500, Frederick Bruckman wrote:
> On Thu, 23 May 2002, Julio Merino wrote:
> The intention is for "pkg_add" to install and register the scripts to
> a holding area, then to have the INSTALL script activate them by
> copying them to "/etc/rc.d/". This can accomodate network mounted
> /usr, shared "${PREFIX}", and build-only machines that won't ever run
> the package. The fact that some people can trivially execute some of
> the scripts directly from the holding area ("${PREFIX}/etc/rc.d")
> isn't relevant -- it doesn't work in general, and it's not
> supportable. Your change won't even be able to support separate root
> and /usr partitions. ${PKG_SYSCONFBASE} doesn't have to be on the root
> file-system, but the scripts must be.

Well well, apart from the patch, I didn't explained what I wanted properly.
If I change PKG_SYSCONFBASE to anywhere else, shouldn't default scripts
get installed there (the ones in the holding area)? So maybe the thing to
do is to fix packages to install their scripts into ${PKG_SYSCONFBASE}/rc.d
and then let move them to /etc/rc.d. What I mean is that
those packages have ${PREFIX}/etc/rc.d into them and the "etc" directory is
controlled by PKG_SYSCONFBASE?

Is this ok?...


Of course it runs NetBSD -
HispaBSD member -
Julio Merino <>

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.0.7 (NetBSD)