caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Damien Doligez <damien.doligez@inria.fr>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 4.01.0+beta1
Date: Thu, 15 Aug 2013 14:58:43 -0400	[thread overview]
Message-ID: <451E5F6A-ECEC-4427-B0BF-FDCE54022321@recoil.org> (raw)
In-Reply-To: <6F52C22F-7B45-4FF3-BE7B-F5BCCB9E85FF@inria.fr>

On 15 Aug 2013, at 13:54, Damien Doligez <damien.doligez@inria.fr> wrote:

> Dear OCaml users,
> 
> The beta version of OCaml 4.01.0 is now available here:
> 
>  http://caml.inria.fr/pub/distrib/ocaml-4.01/
> 
> This is released as source-only, for your testing pleasure. The release candidate is scheduled for the end of this month, so don't please waste time in testing and reporting bugs.

I've added an OPAM switch for this to make it easier to try out, so you should be able to:

$ opam update
$ opam switch 4.01.0beta1
$ opam install lwt core utop

> Compatibility notes:
> 
> The following software will need minor adjustments to run with this release (as compared to the svn version of June 13):
> 
> - camlp5 6.10: warnings.mli has changed. Version 6.11 will be available very soon.
> - obrowser 1.1.1: stdlib/printexc.{ml,mli} have changed (functions added).
> - lwt 2.4.0: otherlibs/unix/unix.mli has one more constructor (O_CLOEXEC) in type open_flag.
> - core-109.37.00: same reason.

I've added local patches for the last two into OPAM so they'll work until the releases catch up.

-anil

  reply	other threads:[~2013-08-15 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 17:54 Damien Doligez
2013-08-15 18:58 ` Anil Madhavapeddy [this message]
2013-08-15 22:46 ` Daniel de Rauglaudre
2013-08-19 12:36 ` Jonathan Protzenko

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=451E5F6A-ECEC-4427-B0BF-FDCE54022321@recoil.org \
    --to=anil@recoil.org \
    --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).