From: Goswin von Brederlow <goswin-v-b@web.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml 4.04.0+beta1
Date: Mon, 5 Sep 2016 11:24:55 +0200 [thread overview]
Message-ID: <20160905092454.GA2590@frosties> (raw)
In-Reply-To: <6376953.JadIDSuSEq@agaric>
On Fri, Aug 26, 2016 at 04:00:15PM +0200, Louis Gesbert wrote:
> I confirm what has been said before: opam follows the Debian convention of having `1.0~foo` < `1.0` < `1.0+foo` ; and you would generally write the constraint as `< 4.04` to exclude `4.04.0~beta` from the range, although for finer constraints you can need a suffix `~`, e.g. `< 4.04.1~` to avoid including `4.04.1~beta`. But constraints shouldn't depend on patch versions right ?
>
> On the other hand, constraints such as `>= 4.04.0` don't include betas if named `4.04.0~beta`, while it would include `4.04.0+beta`
dpkg --compare-versions "4.04.1~" "<<" "4.04.1~beta" && echo yes
yes
Did you mean you need 4.04.1~ to include 4.04.1~beta?
MfG
Goswin
next prev parent reply other threads:[~2016-09-05 9:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 13:15 Damien Doligez
2016-08-09 14:24 ` Goswin von Brederlow
2016-08-11 15:10 ` Damien Doligez
2016-08-11 16:28 ` David Allsopp
2016-08-12 10:47 ` Damien Doligez
2016-08-12 10:58 ` Fabrice Le Fessant
2016-08-12 12:09 ` Damien Doligez
2016-08-12 12:23 ` Daniel Bünzli
2016-08-12 12:25 ` Grégoire Henry
2016-08-12 12:50 ` David Allsopp
2016-08-16 12:37 ` Damien Doligez
2016-08-16 12:44 ` Gabriel Scherer
2016-08-16 12:54 ` David Allsopp
2016-08-26 14:00 ` Louis Gesbert
2016-09-05 9:24 ` Goswin von Brederlow [this message]
2016-08-12 12:46 ` David Allsopp
2016-08-12 14:56 ` [Caml-list] Debian's version-numbering convention Hendrik Boom
2016-08-12 15:57 ` David Allsopp
2016-08-12 16:06 ` Hendrik Boom
2016-08-09 16:06 ` [Caml-list] OCaml 4.04.0+beta1 Mohamed Iguernlala
2016-08-10 16:42 ` Mohamed Iguernlala
2016-08-10 16:46 ` Anil Madhavapeddy
2016-08-12 10:09 ` Fabrice Le Fessant
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=20160905092454.GA2590@frosties \
--to=goswin-v-b@web.de \
--cc=caml-list@inria.fr \
/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