From owner-freebsd-ports@FreeBSD.ORG  Wed May  4 01:07:17 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C96E416A4CE
	for <ports@freebsd.org>; Wed,  4 May 2005 01:07:17 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 762D943D5D
	for <ports@freebsd.org>; Wed,  4 May 2005 01:07:17 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 2826E512D3; Tue,  3 May 2005 18:07:15 -0700 (PDT)
Date: Tue, 3 May 2005 18:07:15 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Edwin Groothuis <edwin@mavetju.org>
Message-ID: <20050504010714.GA85859@xor.obsecurity.org>
References: <Pine.BSF.4.62.0505040238130.76590@acrux.dbai.tuwien.ac.at>
	<20050504010128.GN1175@k7.mavetju>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH"
Content-Disposition: inline
In-Reply-To: <20050504010128.GN1175@k7.mavetju>
User-Agent: Mutt/1.4.2.1i
cc: ports@freebsd.org
cc: Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: How to set CONFLICTS properly?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 May 2005 01:07:17 -0000


--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, May 04, 2005 at 11:01:28AM +1000, Edwin Groothuis wrote:
> On Wed, May 04, 2005 at 02:43:27AM +0200, Gerald Pfeifer wrote:
> > The current definition of CONFLICTS in Mk/bsd.ports.mk reads:
> >=20
> >   # CONFLICTS - A list of package name patterns that the port conflicts=
 with.
> >   #             It's possible to use any shell meta-characters for patt=
ern
> >   #             matching.
> >   #             E.g. apache*-1.2* apache*-1.3.[012345] apache-*+ssl_*
> >=20
> > However, CONFLICTS=3D {gcc-3.3.*,gcc-4.1.*}* fails to detect an install=
ed=20
> > gcc-3.3.6_20050427 port, whereas `ls $PKG_DBDIR/gcc-{3.3.*,4.1.*}` does
> > indeed find the directory in the database.
> >=20
> > Why doesn't that CONFLICTS statement work?
>=20
> I found something funny today:
>=20
>     PREFIX=3D         ${LOCALBASE}
>     CONFLICTS=3D      gcc-3.4* gcc-4.1*
> vs
>     PREFIX=3D         ${X11BASE}
>     CONFLICTS=3D      gcc-3.4* gcc-4.1*
>=20
> Maybe that is also what happens in your case?

CONFLICTS is supposed to register *installation* conflicts, i.e. two
ports that stomp each others files.  Thus, if the port is installed
into a different PREFIX than the installed port (which would stomp
files when both PREFIXes are equal), it will not actually conflict.

Kris


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQFCeCBCWry0BWjoQKURArzjAKCIco9cF7p6PrT0YdmTNyNv5z8sHQCg+Xcq
lrhY9qTCIJiOfrwI09TDtPg=
=+DMs
-----END PGP SIGNATURE-----

--7JfCtLOvnd9MIVvH--