[arch-general] Package versioning

Doug Newgard scimmia at archlinux.info
Thu Sep 1 22:45:51 UTC 2016


On Thu, 1 Sep 2016 23:39:59 +0100
João Miguel via arch-general <arch-general at archlinux.org> wrote:

> A 2016-09-01T23:57:07 +0200, Magnus Therning escreveu:
> > 
> > When packaging Haskell packages there's a bit of a twist to the version
> > numbers that I'm looking for a solution to.
> > 
> > Upstream versions have two numbers, a version number (set by the
> > upstream developer) and an "xrev" that's bumped when minor changes are
> > made to packages on Hackage (Haskell's CPAN/PyPi/RubyGems/...).
> > 
> > Then the packaging has a release.
> > 
> > So far I've been using versions of the form
> > 
> >    <upstream version>_<xrev>-<pkgrel>
> > 
> > But that isn't good enough, `pacman` has for instance reported that's
> > 
> > ~~~
> > warning: haskell-vector-algorithms: local (0.7_1-2) is newer than haskell-core (0.7.0.1_0-1)
> > warning: haskell-monadrandom: local (0.4_2-1) is newer than haskell-core (0.4.1_0-1)
> > ~~~
> > 
> > which isn't correct since
> > 
> >    0.7 < 0.7.0.1
> >    0.4 < 0.4.1
> > 
> > It seems `pacman` treats underbar like a period, which isn't at all what
> > I was hoping for.
> > 
> > I'm hoping for some help to find something better. Any suggestions on
> > how I should do this properly?  
> What do you think about making that xrev part of the pkgrel? Instead of
> 0.7_1-2 you'd have 0.7-1.2 < 0.7.0.1-0.1. And even if haskell-core
> continues using that underscore, 0.7-1.2 < 0.7.0.1_0-1.
> 
> It's not very common to have a decimal Pkgrel, and I'm not sure if it is
> good practice, but I've used it, in fact for Haskell packages in
> particular.
> 
> Regards,
> João Miguel

pkgrel is for Arch specific changes, changes from upstream should be part of
the pkgver.


More information about the arch-general mailing list