Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Apr 2006 17:29:11 -0500
From:      "Scot Hetzel" <swhetzel@gmail.com>
To:        "Doug Barton" <dougb@freebsd.org>, ports@freebsd.org, ports-bugs@freebsd.org, portmgr@freebsd.org
Subject:   Re: HEADS UP: Triage of rcNG related problem reports/USE_RC_SUBR
Message-ID:  <790a9fff0604261529i28967cc1x99679cdd2d334ed9@mail.gmail.com>
In-Reply-To: <20060426220756.GB6337@merlin.emma.line.org>
References:  <20060426203500.GB1433@merlin.emma.line.org> <444FE8F6.2040903@FreeBSD.org> <20060426220756.GB6337@merlin.emma.line.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 4/26/06, Matthias Andree <matthias.andree@gmx.de> wrote:
> 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-in=
stall.html>
> to all packages built for freebsd >=3D 600101 and < 700000 or >=3D 700007=
.
>
> 2. behavior: If the package is about to be installed on a
>   freebsd < 600101 or >=3D 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.
>
The only problem I see is if a port already has a pkg-install script.
How do you append the warning to it?

Scot
--
DISCLAIMER:
No electrons were mamed while sending this message. Only slightly bruised.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff0604261529i28967cc1x99679cdd2d334ed9>