caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ivan Gotovchits <ivg@ieee.org>
To: Jeremie Dimino <jdimino@janestreet.com>
Cc: "ocaml-core@googlegroups.com" <ocaml-core@googlegroups.com>,
	"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Package renamings for sexplib, bin_prot and a few other camlp4 syntax extensions
Date: Tue, 26 Jan 2016 08:57:02 -0500	[thread overview]
Message-ID: <CALdWJ+zpDyTJZ5yfqUh0f83gyEHSGpRuXeyKLXNhW5Z1cDooXQ@mail.gmail.com> (raw)
In-Reply-To: <CANhEzE5agSAzaATJCd7HNRLCfuU3q4LCanQmoePXV2hxUdFzBQ@mail.gmail.com>

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

Hi,

I hope that the change will not modify library names retrospectively? I.e.,
the old versions will be still available under the `.syntax` names?

Also, presumably some tools rely on the `.syntax` extension, maybe it is
better to preserve the extension, i.e., to use `pa_sexp_conv.syntax`?

On Tue, Jan 26, 2016 at 5:44 AM, Jeremie Dimino <jdimino@janestreet.com>
wrote:

> Hi,
>
> In preparation for the 113.24 release of Jane Street packages, which are
> camlp4-free, we moved some Camlp4 syntax extensions into their own packages
> [1]. As a result some findlib packages have been renamed. For instance the
> old sexplib.syntax is now called pa_sexp_conv.
>
> Details and upgrading instructions can be found in the opam repository
> changelog [2].
>
> Since the upcoming 113.24 release of sexplib, bin_prot and a few other
> packages breaks compatibility due to these renamings, version constraints
> were automatically added to the appropriate opam packages.
>
> This is the list of affected packages:
>
> - async-zmq
> - bookaml
> - camlhighlight
> - charrua-core
> - cohttp
> - colors_js
> - conduit
> - cstruct
> - extprot
> - ezjsonm
> - frenetic
> - git-unix
> - ibx
> - ipaddr
> - irmin
> - lambdoc
> - lazy-trie
> - merge-queues
> - merge-ropes
> - mirage
> - mirage-git
> - mirage-http
> - mirage-tc
> - mirage-types
> - mirage-types-lwt
> - mustache
> - nocrypto
> - obeanstalk
> - ocaml-markdown
> - oloop
> - openflow
> - operf-macro
> - opium
> - otr
> - packet
> - perf
> - planck
> - protocol-9p
> - qcow-format
> - shared-block-ring
> - sibylfs
> - sill
> - tls
> - tlstunnel
> - topology
> - uri
> - vchan
> - x509
> - xapi-backtrace
> - xapi-stdext
> - xapi-xenopsd
> - xentropyd
>
> If you maintain any of these packages, you are kindly invited to follow
> the upgrading instructions [2].
>
> Moving forward, we encourage people using any of our Camlp4 syntax
> extensions to switch to their ppx replacements.
>
>  [1] https://github.com/ocaml/opam-repository/pull/5414
>  [2] https://github.com/ocaml/opam-repository/blob/master/CHANGES.md
>
> --
> Jeremie
> ​ Dimino
>

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

  reply	other threads:[~2016-01-26 13:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-26 10:44 Jeremie Dimino
2016-01-26 13:57 ` Ivan Gotovchits [this message]
2016-01-26 14:50   ` Jeremie Dimino
2016-01-26 15:15     ` Ivan Gotovchits
2016-01-26 16:15       ` Jeremie Dimino
2016-01-26 16:56         ` Ivan Gotovchits
2016-01-26 17:17           ` Jeremie Dimino
2016-02-03 10:37             ` Jeremie Dimino
2016-02-03 19:20 ` ygrek
2016-02-05  9:36   ` Jeremie Dimino
2016-03-09 15:56     ` Junsong Li
2016-03-09 16:06       ` Jeremie Dimino
2016-03-09 16:23         ` Junsong Li
2016-03-09 17:16       ` Ivan Gotovchits
2016-03-09 17:31         ` Junsong Li

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=CALdWJ+zpDyTJZ5yfqUh0f83gyEHSGpRuXeyKLXNhW5Z1cDooXQ@mail.gmail.com \
    --to=ivg@ieee.org \
    --cc=caml-list@inria.fr \
    --cc=jdimino@janestreet.com \
    --cc=ocaml-core@googlegroups.com \
    /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).