[pacman-dev] vercmp behavior changed on "1.5b versus 1.5" compare

Miklos Vajna vmiklos at frugalware.org
Sun Jun 15 08:27:31 EDT 2008


On Sun, Jun 15, 2008 at 10:34:34AM +0200, Xavier <shiningxc at gmail.com> wrote:
> > here is what upstream usually does:
> >
> > 1.0pre1<  1.0rc1<  1.0<  1.0a
> >
> 
> what about beta or b?

usually a project uses the alpha/beta _or_ the rc/pre schema, not both.
but yes, this is just one more example about _if_ we want to make the
current (read: before the recent changes) better, then the package
manager needs to know about these releases.

> Currently, there is no special handling so it seems we just have an 
> alphabetical order, that is :
> 1.0 < 1.0a < 1.0alpha < 1.0b < 1.0beta < 1.0p < 1.0pre < 1.0rc
> 
> I am not sure how it was before though, maybe the only difference was 
> that 1.0 was last instead of first?

it was how i described in my previous mail, so:

1.0rc < 1.0 -> good
1.0pre < 1.0 -> good
1.0alpha < 1.0 -> good
1.0beta < 1.0 -> good
1.0a < 1.0 -> bad
1.0b < 1.0 -> bad
1.0b (if 'a' stands for alpha) < 1.0 -> good
1.0b (if 'b' stands for beta) < 1.0 -> good

so it was 6 good vs 2 bad while now it's 6 bad vs 2 good, if i haven't
miscounted something.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/pacman-dev/attachments/20080615/48743e45/attachment.pgp>


More information about the pacman-dev mailing list