caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 4.04.0+beta1
Date: Tue, 16 Aug 2016 14:44:29 +0200	[thread overview]
Message-ID: <CAPFanBHWavAA_U_HP3HdO1XvSz0cfkAmNQpUtV99GMcdfdzLeQ@mail.gmail.com> (raw)
In-Reply-To: <CFC2D68B-51D8-4274-8450-7B6EDDF8B345@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]

I personally use (< "4.03") instead of (< "4.03.0"), and I believe that
this way to rule out 4.03.x versions would remain correct (and readable) if
the negative-"~" convention was adopted, as long we don't use "4.03~foo" as
a version number but rather "4.03.0~foo".

(Note that "4.05~dev" could have the nice effect that software configured
to pessimistically reject future OCaml releases (< 4.05) could still be
built from a development version for testing.)

I must say that this semantics for ~ looks rather nice -- although I agree
that writing foo~~ would be a wart and should be avoided.

On Tue, Aug 16, 2016 at 2:37 PM, Damien Doligez <damien.doligez@inria.fr>
wrote:

>
> > On 2016-08-12, at 14:50, David Allsopp <dra-news@metastack.com> wrote:
> >
> > If such a change were agreed, it would also be possible to alter opam
> lint (or at least opam-repository linting, once that's fully a "thing") to
> display a lint warning/info that things like ocaml {< "4.05"} probably mean
> "ocaml" {< "4.05~~"}.
>
> So every mention of an OCaml version number in every opam package
> description file will have to be suffixed with a ~. And that has to be done
> before we change the OCaml numbering scheme.
>
> And I still don't know what's the upside, except for "that's how Debian
> does it"...
>
> -- Damien
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

[-- Attachment #2: Type: text/html, Size: 2537 bytes --]

  reply	other threads:[~2016-08-16 12:45 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 [this message]
2016-08-16 12:54                   ` David Allsopp
2016-08-26 14:00                     ` Louis Gesbert
2016-09-05  9:24                       ` Goswin von Brederlow
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=CAPFanBHWavAA_U_HP3HdO1XvSz0cfkAmNQpUtV99GMcdfdzLeQ@mail.gmail.com \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@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;
as well as URLs for NNTP newsgroup(s).