unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Brett Gilio" <brettg@gnu.org>
Cc: bandali@gnu.org, julien lepiller <roptat@lepiller.eu>
Subject: Re: OCaml 4.09
Date: Sun, 19 Jan 2020 20:35:31 -0500	[thread overview]
Message-ID: <35FE8AAB-7239-4078-90A4-5D67E45DDA25@lepiller.eu> (raw)
In-Reply-To: <87wo9nry76.fsf@gnu.org>

Le 19 janvier 2020 15:25:01 GMT-05:00, "Ludovic Courtès" <ludo@gnu.org> a écrit :
>Hello!
>
>Brett Gilio <brettg@gnu.org> skribis:
>
>> Short message! I am trying to get our OCaml development system up to
>> shape, as it is currently lagging some versions behind. I have opened
>a
>> wip-ocaml4.09 branch for this work. Here are some of the things that
>> need work that I have identified.
>
>I cannot really help on this, but I noticed that Julien added OCaml
>4.09
>in commit 7b99aa043c4e661fd86cfe25e7b51f5081f42e5d, so perhaps you can
>synchronize on the next steps.  :-)
>
>Happy λ!
>
>Ludo’.

Ah yes, sorry about that! Let's synchronize: we have package-with-explicit-ocaml. Next step is to have package-with-ocaml-4.07, update any package that doesn't work with 4.09 (currently 4.07 is still the default), except for the janestreet packages and dependents. Then switch to 4.09 by default and make janestreet packages use 4.07 instead. Finally, import the new version of the janestreet packages and switch lependents to 4.09.

That should ensure every step is buildable. Wdyt?

  reply	other threads:[~2020-01-20  1:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 20:48 OCaml 4.09 Brett Gilio
2020-01-19 20:25 ` Ludovic Courtès
2020-01-20  1:35   ` Julien Lepiller [this message]
2020-01-21  0:43     ` Julien Lepiller
2020-01-22  2:42       ` Julien Lepiller
2020-01-27  3:01         ` Julien Lepiller

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35FE8AAB-7239-4078-90A4-5D67E45DDA25@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=bandali@gnu.org \
    --cc=brettg@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=roptat@lepiller.eu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).