unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Erik <erikl@posteo.net>
To: guix-devel@gnu.org
Subject: ocaml - how can we get more recent version of core-kernel and common ppx'es
Date: Tue, 18 May 2021 06:21:30 +0000	[thread overview]
Message-ID: <ecde5376b30a7cbc2ef57d08a9e63c38@posteo.net> (raw)

Hi, I have a project that requires a more recent core-kernel and some of 
the ppx'es (such as ppx_fields_conv).

Being very new to guix I've managed to add/update packages for python 
and ruby stuff, but this ocaml.scm file is quite different. There's a 
lot going on which I'm guessing is related to complexities arising from 
the whole ppx transition that happened in the ocaml ecosystem a few 
years ago, or perhaps just to the somewhat unsynchronized way libraries 
move to new versions of the compiler and libs (just speculating here).

Anyway afaict (with my limited guix-fu) I would either need to duplicate 
a whole lot of packages or somehow reorganize things to share 
definitions where it makes sense. Both those options would require some 
coordination with the people who made the ocaml.scm infrastructure 
first, because clearly there are projects out there that need the 
current set of packages to work like they do now and I don't want to 
just post a huge patch that surprises these people.

Can we get a thread going somewhere on adding a recent version of 
ocaml-core-kernel (for the 4.11.1 ocaml package, possibly bumping that 
to 4.11.2 in the process)?

Best regards,
Erik Lovlie


             reply	other threads:[~2021-05-18 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  6:21 Erik [this message]
2021-05-18 20:29 ` [bug#47768] ocaml - how can we get more recent version of core-kernel and common ppx'es pukkamustard
2021-05-18 20:58   ` erikl
2021-05-29 22:01   ` Erik

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=ecde5376b30a7cbc2ef57d08a9e63c38@posteo.net \
    --to=erikl@posteo.net \
    --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).