Date: Wed, 4 May 2005 11:01:28 +1000 From: Edwin Groothuis <edwin@mavetju.org> To: Gerald Pfeifer <gerald@pfeifer.com> Cc: ports@freebsd.org Subject: Re: How to set CONFLICTS properly? Message-ID: <20050504010128.GN1175@k7.mavetju> In-Reply-To: <Pine.BSF.4.62.0505040238130.76590@acrux.dbai.tuwien.ac.at> References: <Pine.BSF.4.62.0505040238130.76590@acrux.dbai.tuwien.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 04, 2005 at 02:43:27AM +0200, Gerald Pfeifer wrote:
> The current definition of CONFLICTS in Mk/bsd.ports.mk reads:
>
> # CONFLICTS - A list of package name patterns that the port conflicts with.
> # It's possible to use any shell meta-characters for pattern
> # matching.
> # E.g. apache*-1.2* apache*-1.3.[012345] apache-*+ssl_*
>
> However, CONFLICTS= {gcc-3.3.*,gcc-4.1.*}* fails to detect an installed
> gcc-3.3.6_20050427 port, whereas `ls $PKG_DBDIR/gcc-{3.3.*,4.1.*}` does
> indeed find the directory in the database.
>
> Why doesn't that CONFLICTS statement work?
I found something funny today:
PREFIX= ${LOCALBASE}
CONFLICTS= gcc-3.4* gcc-4.1*
vs
PREFIX= ${X11BASE}
CONFLICTS= gcc-3.4* gcc-4.1*
Maybe that is also what happens in your case?
Edwin
--
Edwin Groothuis | Personal website: http://www.mavetju.org
edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050504010128.GN1175>