On Mon, Feb 03, 2020 at 09:09:25PM +0000, Stuart Henderson wrote:
> > @@ -1,7 +1,9 @@
> > @comment $OpenBSD: PLIST-gdbm,v 1.4 2019/12/11 19:55:40 sthen Exp $
> > @option no-default-conflict
> > @option is-branch
> > -@conflict python-gdbm->=3.7,<3.8
> > +@conflict python-gdbm->=3,<3.8
>
> this should be split in two ("conflict with 'this' version of python" which
> should be present for all subpkgs, and "conflict with old versions to provide
> an upgrade path").
Hm.. I don't understand why this needs to be two separate lines, when
union of those gives the same constraint result.
$ env TRUSTED_PKG_PATH=/home/ports/packages/aarch64/all/ pkg_info -f
python-3.7.6p0
@conflict python->=3.7,<3.8
@conflict python->=3.2,<3.7
@pkgpath lang/python/3.2,-main
@pkgpath lang/python/3.3,-main
@pkgpath lang/python/3.4,-main
@pkgpath lang/python/3.5,-main
@pkgpath lang/python/3.6,-main
Above two conflict markers basically mean `@conflict python->=3.2,<3.8`.
Stuart, can you elaborate why separating conflict marker into two is
necessary? Is this just to make it clear conceptually what is going on
and help with further upgrade paths (py 3.8, 3.9, 3.10, etc.)?
--
Regards,
Mikolaj
