On 2022/11/19 09:00, Laurence Tratt wrote: > On Fri, Nov 18, 2022 at 01:38:06PM -0700, Anthony J. Bentley wrote: > > Hello Anthony, > > > When a version number decreases like libvterm's does, the port needs to set > > EPOCH so the smaller number is considered newer. Without it package > > upgrades won't work either. > > Aha, I did not know about EPOCH! > > The attached updates take this, and other comments, into account, and is > hopefully ready for import. > > > Laurie
> diff --git editors/neovim/Makefile editors/neovim/Makefile > index ef5028b973a..cd5db22b26d 100644 > --- editors/neovim/Makefile > +++ editors/neovim/Makefile > @@ -13,7 +13,7 @@ COMMENT = continuation and extension of Vim > > GH_ACCOUNT = neovim > GH_PROJECT = neovim > -GH_TAGNAME = v0.7.2 > +GH_TAGNAME = v0.8.0 > > CATEGORIES = editors devel > HOMEPAGE = https://neovim.io > @@ -62,7 +62,7 @@ BUILD_DEPENDS = ${RUN_DEPENDS} \ > LIB_DEPENDS = devel/gettext,-runtime \ > devel/libtermkey \ > devel/libuv \ > - devel/libvterm \ > + devel/libvterm>=0.3 \ This would need to be 0.3v0 to take EPOCH into account (otherwise libvterm-20191009 matches). I don't object to listing a version spec, but I would simply not bother with it here though. ports doesn't really support building unless you have the whole tree updated - and partial package updates don't work at all well. The main use I find for version specs in dependencies is to annotate when something is known to require a version *lower* than a specific version, or when a port is present in multiple versions (autoconf, python, lua, etc).
