Am 02.09.2016 um 11:03 schrieb Magnus Therning:
Yes, it looks like it would work better. Is there some description of
what the presence of a letter actually means?
/M
The manpage for vercmp describes it with some examples:
Version comparison operates as follows:
Alphanumeric:
On Fri, 02 Sep 2016 11:03:50 +0200
Magnus Therning wrote:
> Doug Newgard writes:
> > Sounds like .x would make more sense.
>
> Yes, it looks like it would work better. Is there some description of
> what the presence of a letter actually means?
>
> /M
>
Simply put, letters are less than nu
On 09/02/2016 05:03 AM, Magnus Therning wrote:
> Yes, it looks like it would work better. Is there some description of
> what the presence of a letter actually means?
IIUC, it separates two individual components of the versioning,
everything before it is considered on its own and the component wit
Doug Newgard writes:
> On Thu, 01 Sep 2016 23:57:07 +0200
> Magnus Therning wrote:
>
>> 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 deve
On Thu, 1 Sep 2016 23:39:59 +0100
João Miguel via arch-general 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 numbe
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 w
On 09/01/2016 06:04 PM, Doug Newgard wrote:
>> 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.
>
> Sounds like .x would make more sense.
And similarly, *-git packages usually use
On Thu, 01 Sep 2016 23:57:07 +0200
Magnus Therning wrote:
> 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 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/P
9 matches
Mail list logo
