On 2017년 03월 20일 11:46, IOhannes m zmoelnig wrote:
On 2017-03-20 09:57, Max wrote:
Looks correct, no?
[...]
On 2017년 03월 20일 09:53, Roman Haefeli wrote:
0.1~git20170101 > 0.1
the "~" is a common trick (e.g. with Debian packages) for pre-release
versions.
my expectation would be:
- 0.0
-
On 2017-03-20 09:57, Max wrote:
> Looks correct, no?
>
[...]
> On 2017년 03월 20일 09:53, Roman Haefeli wrote:
>> 0.1~git20170101 > 0.1
the "~" is a common trick (e.g. with Debian packages) for pre-release
versions.
my expectation would be:
- 0.0
- 0.1~git20170101
- 0.1
- 0.1+thistimeforreal
-
On Mon, 2017-03-20 at 09:57 +0100, Max wrote:
> Looks correct, no?
According to what? I was rather wondering about the semantics than
pointing out that something is broken.
IOhannes mentioned how it works in the meanwhile.
Roman
signature.asc
Description: This is a digitally signed message
On Mon, 2017-03-20 at 10:12 +0100, IOhannes m zmoelnig wrote:
> On 2017-03-20 09:53, Roman Haefeli wrote:
> > Is it actually
> > simply
> > an alphabetical sort?
> no. deken *tries* to do a semantic sort.
>
> this is done using tcl's "lsort -dictionary" [1].
Ah, thanks.
> it correctly sorts
On 2017-03-20 09:53, Roman Haefeli wrote:
> Hey
>
> How does Deken compare versions? I noticed that Deken interprets:
>
> 1.1.1 > 1.1
>
> and
>
> 0.1~git20170101 > 0.1
>
> Looks similar to the output of the sort command. Is it actually simply
> an alphabetical sort?
no. deken *tries* to do a
Looks correct, no?
On 2017년 03월 20일 09:53, Roman Haefeli wrote:
Hey
How does Deken compare versions? I noticed that Deken interprets:
1.1.1 > 1.1
and
0.1~git20170101 > 0.1
Looks similar to the output of the sort command. Is it actually simply
an alphabetical sort?
Roman
