All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Fleischer <mlmmj@cryptocrack.de>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Mlmmj 1.2.18a1 released
Date: Sat, 17 Mar 2012 12:16:26 +0000	[thread overview]
Message-ID: <20120317121626.GA28513@blizzard> (raw)
In-Reply-To: <4F5E32B9.6090908@yahoo.com.au>

On Thu, Mar 15, 2012 at 10:51:02PM +1100, Ben Schmidt wrote:
> >>>>An alpha release for the upcoming Mlmmj 1.2.18 has been published.
> >
> >Works fine so far. Didn't notice any regression.
> 
> Thanks a lot for the feedback.
> 
> >>>Later, if you publish 1.2.18.0, it's going to be considered smaller
> >>>than 1.2.18a1
> 
> In trying to figure out a better scheme, I disproved it for Debian:
> 
> $ dpkg --compare-versions 1.2.18a1 lt 1.2.18.0 && echo YES || echo NO
> YES
> 
> It's a problem if the final .0 is omitted:
> 
> $ dpkg --compare-versions 1.2.18a1 lt 1.2.18 && echo YES || echo NO
> NO
> 
> That is what I would have done, but due to this issue, I'm happy enough
> to include the final .0 as occasionally we do have three-point releases
> anyway, and this may be the best solution.

Oh, I didn't even notice the missing revision/build part. Yeah, should
should include that...

> 
> >Yeah, this is used by several projects and shouldn't cause any
> >trouble... It works under Arch Linux (pacman, which uses a version
> >comparison algorithm ripped off from RPM):
> >
> >     $ vercmp 1.2.17.0 1.2.18.0
> >     -1
> >     $ vercmp 1.2.18.0a1 1.2.18.0
> >     -1
> 
> What about
> 
> $ vercmp 1.2.18a1 1.2.18.0

It is pretty clever:

    $ vercmp 1.2.18a1 1.2.18.0
    -1

... :)

> 
> ?
> 
> Smiles,
> 
> Ben.
> 
> 
> 


  parent reply	other threads:[~2012-03-17 12:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 17:30 [mlmmj] Mlmmj 1.2.18a1 released Ben Schmidt
2012-03-13  7:16 ` Thomas Goirand
2012-03-13 12:14 ` Ben Schmidt
2012-03-13 20:07 ` Lukas Fleischer
2012-03-15 11:51 ` Ben Schmidt
2012-03-17 12:16 ` Lukas Fleischer [this message]
2012-03-17 15:52 ` Ben Schmidt
2012-05-02 16:41 ` Quentin Heath

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=20120317121626.GA28513@blizzard \
    --to=mlmmj@cryptocrack.de \
    --cc=mlmmj@mlmmj.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.