How to set CONFLICTS properly?

[Kris Kennaway]

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:
> > 
> >   # 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?

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050503/29d6d680/attachment.bin