Date: Thu, 27 Apr 2006 00:07:56 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: Doug Barton <dougb@freebsd.org> Cc: ports@freebsd.org, portmgr@freebsd.org, ports-bugs@freebsd.org Subject: Re: HEADS UP: Triage of rcNG related problem reports/USE_RC_SUBR Message-ID: <20060426220756.GB6337@merlin.emma.line.org> In-Reply-To: <444FE8F6.2040903@FreeBSD.org> References: <20060426203500.GB1433@merlin.emma.line.org> <444FE8F6.2040903@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 26 Apr 2006, Doug Barton wrote: > Matthias Andree wrote: > > > It is a bit unfortunate that there is no accompanying security branch > > for ports, because then this inconsistency WRT etc/rc.d/* scripts > > wouldn't have bitten users. > > This is a period of change, which unfortunately necessitates some small > amount of pain in the short term. Sorry to hear that this aspect of the > change is causing you difficulty. It's not causing _me_ difficulty, but unskilled users, and that's much less desirable. I am with RELENG_6 where the current ports work nicely. And I do have an idea to protect the innocent from installing 6.1 packages on 6.0-RELEASE: 1. Add a PRE-INSTALL mode pkg-install script <http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/pkg-install.html>; to all packages built for freebsd >= 600101 and < 700000 or >= 700007. 2. behavior: If the package is about to be installed on a freebsd < 600101 or >= 700000 and < 700007, the pre-install script complains, asks the user to use the port instead and exits, aborting the install with an error. As portsnap and portmaster are deployed, that's something that shouldn't be too difficult to explain. This could all be handled inside ports/Mk/bsd.port.mk. -- Matthias Andree
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060426220756.GB6337>