On 2020-09-18 08:48, Kurt Mosiejczuk wrote:
On Fri, Sep 18, 2020 at 06:52:50AM +0200, Bjorn Ketelaars wrote:
On Thu 17/09/2020 21:31, Pamela Mosiejczuk wrote:
www/py-vcrpy has removed the python 2 flavor, and with the preceding
update to that, we can remove the python 2 flavor on test-vcr.
OK?
One question:
Index: pkg/PLIST
===================================================================
RCS file: /home/cvs/ports/devel/py-test-vcr/pkg/PLIST,v
retrieving revision 1.1.1.1
diff -u -p -r1.1.1.1 PLIST
--- pkg/PLIST 19 Nov 2019 00:03:08 -0000 1.1.1.1
+++ pkg/PLIST 18 Sep 2020 01:21:08 -0000
@@ -1,4 +1,6 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2019/11/19 00:03:08 pamela Exp $
+@conflict py-test-vcr-<=1.0.2
Is there a need for this conflict marker to be version specific? Why not
just use '@conflict py-test-vcr-*'?
Does it really make a difference?
--Kurt
Looks like a consistent convention... when I looked again, constructing
it with <=
the conflict line was for a different port than the one included, which
makes sense
if this is usually handled elsewhere.
