caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Allsopp <dra-news@metastack.com>
To: Damien Doligez <damien.doligez@inria.fr>,
	caml users <caml-list@inria.fr>
Subject: RE: [Caml-list] OCaml 4.04.0+beta1
Date: Tue, 16 Aug 2016 12:54:48 +0000	[thread overview]
Message-ID: <E51C5B015DBD1348A1D85763337FB6D901350A365E@Remus.metastack.local> (raw)
In-Reply-To: <CFC2D68B-51D8-4274-8450-7B6EDDF8B345@inria.fr>

Damien Doligez 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.

Yes, but as far as OPAM packages are concerned, it sounds as though that's what we "should" already be doing. It's also something that can be done mechanically (cf. the removal of ocamlbuild in 4.03.0).

> And I still don't know what's the upside, except for "that's how Debian
> does it"...

It would mean that OPAM would be automatically clear that the release version (4.05.0) is superior to the release candidate (4.05.0~rc1) - that's philosophically nice, if nothing else. That said, I don't think there's any technical reason why the OPAM package version has to match the OCaml version exactly; it'd just be mildly confusing.


David

  parent reply	other threads:[~2016-08-16 12:54 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 [this message]
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=E51C5B015DBD1348A1D85763337FB6D901350A365E@Remus.metastack.local \
    --to=dra-news@metastack.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).