From: Brett Gilio <brettg@gnu.org>
To: guix-devel@gnu.org
Cc: bandali@gnu.org
Subject: OCaml 4.09
Date: Wed, 15 Jan 2020 14:48:28 -0600 [thread overview]
Message-ID: <87lfq8win7.fsf@gnu.org> (raw)
Hey all,
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.
-- The opam importer needs revised and updated.
-- Basically all of the Jane Street components need reimported and
modified.
-- The dune build system probably needs to be able to handle two
versions of dune without complication.
-- We need to create some unison packages for things like
dune-configuration.
-- Basically all OCaml dependent packages need to get rebuilt and
tested, ensuring that test cases are also appropriately handled (some
are disabled that could easily be enabled.)
-- Get our OCaml development components up to date and working, like
ocamlformat, merlin, tuareg, the ocaml-lsp system (forked off of
merlin).
-- Potentially add a Coq subimporter for opam.
-- Be able to have variant compilers for ocaml-flambda (and the upcoming
ocaml-multicore) switches.
If any of these tasks interest you, I challenge you to help! :). I am
trying my best to do it myself so far, but I am running on a very
limited amount of contribution time these next couple of weeks. This is
an important task, too, for us Formal Methods people in the Guix
community, as a lot of formal methods utilities run on OCaml.
Carry on! Thanks.
--
Brett M. Gilio
GNU Guix, Contributor | GNU Project, Webmaster
[DFC0 C7F7 9EE6 0CA7 AE55 5E19 6722 43C4 A03F 0EEE]
<brettg@gnu.org> <brettg@posteo.net>
next reply other threads:[~2020-01-15 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 20:48 Brett Gilio [this message]
2020-01-19 20:25 ` OCaml 4.09 Ludovic Courtès
2020-01-20 1:35 ` Julien Lepiller
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=87lfq8win7.fsf@gnu.org \
--to=brettg@gnu.org \
--cc=bandali@gnu.org \
--cc=guix-devel@gnu.org \
/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).