Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 3 May 2005 18:07:15 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Edwin Groothuis <edwin@mavetju.org>
Cc:        Gerald Pfeifer <gerald@pfeifer.com>
Subject:   Re: How to set CONFLICTS properly?
Message-ID:  <20050504010714.GA85859@xor.obsecurity.org>
In-Reply-To: <20050504010128.GN1175@k7.mavetju>
References:  <Pine.BSF.4.62.0505040238130.76590@acrux.dbai.tuwien.ac.at> <20050504010128.GN1175@k7.mavetju>

next in thread | previous in thread | raw e-mail | index | archive | help

--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--



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