From: Junsong Li <ljs.darkfish@gmail.com>
To: Jeremie Dimino <jdimino@janestreet.com>
Cc: "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: Wed, 9 Mar 2016 08:23:16 -0800 [thread overview]
Message-ID: <CA+kGxtNRxHyay7QsvAPzMaODAH-oLAT48h2vF3TFunegiEUPMA@mail.gmail.com> (raw)
In-Reply-To: <CANhEzE6bkmsxM6n==f9hmnAS0fqbWaDmvZ0ywDrAb0NA0_8iYA@mail.gmail.com>
Ah, I see
$ opam upgrade --verbose sexplib
Everything as up-to-date as possible.
The following newer versions couldn't be installed:
- sexplib.113.24.00 is not available because your system doesn't
comply with ocaml-version >= "4.02.3".
I'll install OCaml 4.02.3 then.
Thank you.
On Wed, Mar 9, 2016 at 8:06 AM, Jeremie Dimino <jdimino@janestreet.com> wrote:
> Hi Junsong,
>
> It's possible that you have a package installed that has no version
> compatible with sexplib 113.24. You can try to explicitly upgrade sexplib to
> see what solution opam suggests
>
> On Wed, Mar 9, 2016 at 3:56 PM, Junsong Li <ljs.darkfish@gmail.com> wrote:
>>
>> Hi Jeremie,
>>
>> I have 4.02.1 OCaml installed on my Mac. opam update; opam upgrade
>> didn't upgrade the sexplib to 113.24. opam list still shows 113.00.
>> Any ideas?
>>
>> My fresh installed 4.02.3 OCaml on a Linux machine has 113.24 sexplib
>> though.
>>
>> On Fri, Feb 5, 2016 at 1:36 AM, Jeremie Dimino <jdimino@janestreet.com>
>> wrote:
>> > On Wed, Feb 3, 2016 at 7:20 PM, ygrek <ygrek@autistici.org> wrote:
>> >>
>> >> I wonder if keeping empty sexplib.syntax subpackage with only
>> >> requires="pa_sexp_conv" line
>> >> will prevent build breakage (one will only need to fix opam
>> >> dependencies)?
>> >
>> >
>> > That would work for now. However, sooner or latter some change in
>> >
>> > sexplib will break the code generated by pa_sexp_conv and we'll have the
>> > same problem again.
>> > The current forced upgrade is simple (one sed command [1]) and it's a
>> > hint
>> > that it's a good time to switch to ppx. We published a tool to help with
>> > this BTW [2]
>> >
>> > [1] https://github.com/ocaml/opam-repository/blob/master/CHANGES.md
>> > [2]
>> > https://blogs.janestreet.com/converting-a-code-base-from-camlp4-to-ppx
>> >
>> > https://github.com/janestreet/camlp4-to-ppx
>> >
>> > --
>> > Jeremie
>
>
>
>
> --
> Jeremie
next prev parent reply other threads:[~2016-03-09 16:23 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
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 [this message]
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=CA+kGxtNRxHyay7QsvAPzMaODAH-oLAT48h2vF3TFunegiEUPMA@mail.gmail.com \
--to=ljs.darkfish@gmail.com \
--cc=caml-list@inria.fr \
--cc=jdimino@janestreet.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).