The other port has `@conflict z3-*', devel/z3 fails to install on first
try:
# pkg_add z3
quirks-3.273->3.283: ok
Collision in z3-4.8.6: the following files already exist
/usr/local/bin/z3 (py3-z3-solver-4.8.7.0 and z3-4.8.6)
...
Read shared items: ok
Couldn't install z3-4.8.6
Strangely enough, successive pkg_add attempts behave as if the conflict
marker was installed:
# pkg_add z3
quirks-3.283 signed on 2020-03-21T17:14:41Z
Can't install z3-4.8.6 because of conflicts (py3-z3-solver-4.8.7.0)
--- z3-4.8.6 -------------------
Can't install z3-4.8.6: conflicts
Couldn't install z3-4.8.6
I don't know that pkg_add(1) does under the hood and pkg_create(1) is
not specific enough about whether conflicts need to be registered in
all effected ports:
@conflict pkgspec
Declare a conflict with packages matching pkgspec (see
packages-specs(7)). The pkgname package can not be installed if
a package matching pkgspec has been installed because they
install the same files and thus conflict.
But I suppose having @conflict in devel/z3 would handle the first
pkg_add attempt properly.
Feedback? OK?
Index: Makefile
===================================================================
RCS file: /cvs/ports/math/z3/Makefile,v
retrieving revision 1.18
diff -u -p -r1.18 Makefile
--- Makefile 19 Oct 2019 09:42:20 -0000 1.18
+++ Makefile 22 Mar 2020 13:09:20 -0000
@@ -10,6 +10,7 @@ GH_TAGNAME = ${GH_PROJECT}-${VERSION}
DISTNAME = ${GH_TAGNAME}
PKGNAME = ${DISTNAME:L}
+REVISION = 0
SHARED_LIBS = z3 2.0 # 4.8
Index: pkg/PLIST
===================================================================
RCS file: /cvs/ports/math/z3/pkg/PLIST,v
retrieving revision 1.6
diff -u -p -r1.6 PLIST
--- pkg/PLIST 19 Oct 2019 09:42:20 -0000 1.6
+++ pkg/PLIST 22 Mar 2020 13:09:41 -0000
@@ -1,4 +1,5 @@
@comment $OpenBSD: PLIST,v 1.6 2019/10/19 09:42:20 rsadowski Exp $
+@conflict py3-z3-solver-*
@bin bin/z3
include/z3++.h
include/z3.h
