From owner-freebsd-ports@FreeBSD.ORG  Wed May  4 01:01:37 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 5D1D416A4CE
	for <ports@freebsd.org>; Wed,  4 May 2005 01:01:37 +0000 (GMT)
Received: from mail2out.barnet.com.au (mail2out.barnet.com.au [202.83.176.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 861D643D67
	for <ports@freebsd.org>; Wed,  4 May 2005 01:01:36 +0000 (GMT)
	(envelope-from edwin@mavetju.org)
Received: by mail2out.barnet.com.au (Postfix, from userid 27)
	id 522A5707472; Wed,  4 May 2005 11:01:32 +1000 (EST)
X-Viruscan-Id: <42781EEC00006BB9D67240@BarNet>
Received: from mail2-auth.barnet.com.au (mail2.barnet.com.au [202.83.176.13])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	Authority" (verified OK))
	by mail2.barnet.com.au (Postfix) with ESMTP id BF0D670746C;
	Wed,  4 May 2005 11:01:31 +1000 (EST)
Received: from k7.mavetju (edwin-3.int.barnet.com.au [10.10.12.2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	Certificate Authority" (not verified))
	by mail2-auth.barnet.com.au (Postfix) with ESMTP id 1D323707461;
	Wed,  4 May 2005 11:01:31 +1000 (EST)
Received: by k7.mavetju (Postfix, from userid 1001)
	id DB9A56490; Wed,  4 May 2005 11:01:28 +1000 (EST)
Date: Wed, 4 May 2005 11:01:28 +1000
From: Edwin Groothuis <edwin@mavetju.org>
To: Gerald Pfeifer <gerald@pfeifer.com>
Message-ID: <20050504010128.GN1175@k7.mavetju>
References: <Pine.BSF.4.62.0505040238130.76590@acrux.dbai.tuwien.ac.at>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.BSF.4.62.0505040238130.76590@acrux.dbai.tuwien.ac.at>
User-Agent: Mutt/1.5.6i
cc: ports@freebsd.org
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:01:37 -0000

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/