Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-05-03 Thread Fabien Dubosson
In case you were not aware of it, pacman provides an executable named vercmp to compare versions. It also provides a vercmp manpage to explain how ALPM's version comparison function works. $ vercmp 2.1_1 2.1.1_0 -1 I wasn't aware, thanks for the tip! The underscore system seems to work

Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-05-02 Thread Xyne
On 2015-04-30 08:25 +0200 Fabien Dubosson wrote: The issue I'm worried about is that of trailing zeroes. Is 2.1_1 2.1.1_0? warning: downgrading package dummy (2.1.1_0-1 = 2.1_1-1) In case you were not aware of it, pacman provides an executable named vercmp to compare versions. It also

Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-04-30 Thread SP
On 30/04/15 06:55, Fabien Dubosson wrote: The `pkgrel' must be an integer incremented by 1, but there are no defined format for `pkgver'. So why not using `pkgver_xrev-pkgrel' in which `pkgver_xrev' is the `pkgver' defined in the PKGBUILD? It is allowed to do so, will be strictly incrementing

Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-04-30 Thread Fabien Dubosson
The issue I'm worried about is that of trailing zeroes. Is 2.1_1 2.1.1_0? Seems so: === $ mkdir TEMP; cd TEMP $ cat EOL PKGBUILD pkgname=dummy pkgver=2.1.1_0 pkgrel=1 pkgdesc=dummy package arch=(any) url=http://; license=('GPL') source=() md5sums=() package() {

Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-04-30 Thread Magnus Therning
On 30 April 2015 at 07:55, Fabien Dubosson fabien.dubos...@gmail.com wrote: So, instead of dealing with a pair of `(pgkver, pkgrel)` we now have a triple of `(pkgver,xrev,pkgrel)`. The issue then becomes how to convert this triple into a pair. In particular, how to do it so the version

[arch-haskell] RFQ: Proposal for new versioning of packages

2015-04-29 Thread Magnus Therning
I've slowly been working away on some way to deal with the addition of x-revisions in Cabal files. My plan at the moment is to include it in the `pkgrel` in this way haskell-zlib-0.5.4.2-76-x86_64.pkg.tar.xz becomes haskell-zlib-0.5.4.2-0.76-x86_64.pkg.tar.xz given that the x-revision is

Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-04-29 Thread Xyne
On 2015-04-29 22:11 +0200 Magnus Therning wrote: I've slowly been working away on some way to deal with the addition of x-revisions in Cabal files. My plan at the moment is to include it in the `pkgrel` in this way haskell-zlib-0.5.4.2-76-x86_64.pkg.tar.xz becomes

Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-04-29 Thread Magnus Therning
On 30 April 2015 at 01:10, Xyne x...@archlinux.ca wrote: On 2015-04-29 22:11 +0200 Magnus Therning wrote: I've slowly been working away on some way to deal with the addition of x-revisions in Cabal files. My plan at the moment is to include it in the `pkgrel` in this way

Re: [arch-haskell] RFQ: Proposal for new versioning of packages

2015-04-29 Thread Fabien Dubosson
So, instead of dealing with a pair of `(pgkver, pkgrel)` we now have a triple of `(pkgver,xrev,pkgrel)`. The issue then becomes how to convert this triple into a pair. In particular, how to do it so the version ordering rules that `pacman` uses results in the wanted behaviour. The `pkgrel'