Re: Re: RFC: Alternate patch to have true new-style rc.d scripts in ports (without touching localpkg)

From: Scot Hetzel <swhetzel_at_gmail.com>
Date: Tue, 17 Aug 2004 10:09:25 -0500
On Tue, 17 Aug 2004 10:08:12 +0200, Jan Srzednicki <w_at_expro.pl> wrote:
> On Tue, Aug 17, 2004 at 01:10:09AM +0200, Oliver Eikemeier wrote:
> > Mike Makonnen wrote:
> >
> > >I have thought about this considerably, and I think the best solution
> > >is to have ports rc.d scripts installed to /etc/rc.d.
> >
> > This is what I currently do with slapd, but this approach has multiple
> > problems:
> >
> > - it violates the law that packages have to be PREFIX-clean, which has
> > some very unfortunate consequences from a packaging point of view.
> 
> Indeed, unfortunately.
> 
> > - mergemaster barfs ever time (PR 64476)
> 
> That's why my suggestion would be: /etc/rc.d/local/ (or
> /etc/rc.d/ports/, or whatever you want to call it). In this way you can
> easily separate both directories, and as new-style ports rc-scripts have
> to be placed in the new location, there is absolutely no confusion about
> them. Old scripts in /usr/local/etc/rc.d would be run with localpkg as
> they have been before.
> 
Except this breaks for people who are NFS mounting /usr/local from
another machine, as the startup scripts are on the machine where the
port was originally installed, instead on in local/etc/rc.d.  Which is
one of the purposes of putting them into local/etc/rc.d in the first
place.

Scot
Received on Tue Aug 17 2004 - 13:09:47 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:06 UTC