How to set CONFLICTS properly?

Edwin Groothuis edwin at mavetju.org
Tue May 3 18:01:37 PDT 2005


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 at mavetju.org    |          Weblog: http://weblog.barnet.com.au/edwin/


More information about the freebsd-ports mailing list