From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Subject: Re: upset, genini: different version ordering
Date: Mon, 20 Jul 2015 18:10:00 -0000 [thread overview]
Message-ID: <55AD399D.7020001@dronecode.org.uk> (raw)
In-Reply-To: <87380i671e.fsf@Rainer.invalid>
On 20/07/2015 19:03, Achim Gratz wrote:
>
> I've just found that upset and genini will order versions differently.
> For perl-Carp, genini produces:
>
> version: 1.36-1
> [prev]
> version: 1.3301-2
>
> while upset comes up with:
>
> version: 1.3301-2
> [prev]
> version: 1.36-1
>
> For the way Perl distributions are versioned, genini is correct here
> (although it would fail when a distribution switches from x.y.z
> versioning to canonical x.y versioning as PDL has done in the past).
>
> Upset seems to order based on the individual parts in the split version
> string? In any case, at least for Perl distributions it should rather
> use version objects.
>
> http://search.cpan.org/~jpeacock/version-0.9912/lib/version.pod
If I recall correctly, genini is just broken, doing some kind of lexical
sort which e.g. sorts 1.10 before 1.9.
next prev parent reply other threads:[~2015-07-20 18:10 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 18:03 Achim Gratz
2015-07-20 18:10 ` Jon TURNEY [this message]
2015-07-20 18:42 ` Achim Gratz
2015-07-20 19:00 ` Corinna Vinschen
2015-07-20 20:09 ` Achim Gratz
2015-07-21 6:56 ` Corinna Vinschen
2015-07-21 16:59 ` Achim Gratz
2015-07-21 18:49 ` Corinna Vinschen
2015-07-21 19:13 ` Achim Gratz
2015-07-22 9:43 ` Corinna Vinschen
2015-07-22 16:21 ` Achim Gratz
2015-07-23 9:59 ` Corinna Vinschen
2015-07-23 17:09 ` Achim Gratz
2015-07-23 19:17 ` Corinna Vinschen
2015-07-23 19:29 ` Corinna Vinschen
2015-07-23 19:38 ` Achim Gratz
2015-07-23 19:51 ` Corinna Vinschen
2015-07-23 20:02 ` Achim Gratz
2015-07-24 9:19 ` Corinna Vinschen
2015-07-24 18:09 ` Achim Gratz
2015-07-24 18:16 ` Achim Gratz
2015-10-09 13:24 ` Jon Turney
2015-10-19 15:42 ` Corinna Vinschen
2015-10-19 17:19 ` Achim Gratz
2015-10-19 17:28 ` Yaakov Selkowitz
2015-10-19 18:13 ` Achim Gratz
2015-10-20 10:27 ` Corinna Vinschen
2015-10-20 13:33 ` Jon Turney
2015-10-20 15:50 ` Corinna Vinschen
2015-10-20 17:03 ` Yaakov Selkowitz
2015-10-20 19:18 ` Corinna Vinschen
2015-10-20 19:53 ` Achim Gratz
2015-10-20 20:35 ` Yaakov Selkowitz
2015-10-21 16:45 ` Achim Gratz
2015-10-21 17:04 ` Yaakov Selkowitz
2015-11-20 19:14 ` Jon Turney
2015-10-20 13:47 ` Jon Turney
2015-10-20 17:29 ` Achim Gratz
2015-08-18 18:34 ` Achim Gratz
2015-08-18 19:06 ` Corinna Vinschen
2015-08-18 20:07 ` Achim Gratz
2015-08-19 8:25 ` Corinna Vinschen
2015-08-21 13:28 ` Corinna Vinschen
2015-08-21 18:35 ` Achim Gratz
2015-08-22 10:48 ` Achim Gratz
2015-08-22 10:51 ` Achim Gratz
2015-08-22 13:29 ` Corinna Vinschen
2015-08-22 15:11 ` Achim Gratz
2015-08-24 7:27 ` Corinna Vinschen
2015-09-03 16:34 ` Corinna Vinschen
2015-08-20 11:37 ` Jon TURNEY
2015-08-20 19:55 ` Achim Gratz
2015-08-24 11:25 ` Yaakov Selkowitz
2015-08-24 12:29 ` Corinna Vinschen
2015-08-24 17:13 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55AD399D.7020001@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).