Re: package version numbering change

[Jonathan Perkin <jperkin%joyent.com@localhost>]

* On 2019-09-11 at 13:25 BST, Manuel Bouyer wrote:

> On Tue, Sep 10, 2019 at 08:03:22PM -0400, Greg Troxel wrote:
> > Manuel Bouyer <bouyer%antioche.eu.org@localhost> writes:
> > 
> > > Hello,
> > > upstream for geography/opencpn-plugin-watchdog changed, and there is
> > > now properly tagged releases. So I'd like to switch to new upstream
> > > and use release tags. But this would mean that the package version would
> > > go from 20190228 to 2.4.6.
> > >
> > > Won't the pkg tools think that 2.4.6 is older than 20190228 ?
> > > If so what's the best way to deal with this ?
> > 
> > My vote is just to do this, and blame any manual work people have to do
> > on upstream.  I supsect it's not a lot of total effort (pkg_delete,
> > pkg_add the new one, once) times not a lot of people, and that seems
> > better than baggage from some epoch scheme forever.
> 
> Actually pkg_add -u will update from 20190228 to 2.4.6.
> But pkgin ug will not (I just tried).

ug or fug?  ug will only upgrade non-automatic packages.

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com