unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: DABY-SEESARAM Arnaud <ds-ac@nanein.fr>
To: pukkamustard <pukkamustard@posteo.net>
Cc: guix-devel <guix-devel@gnu.org>, Julien Lepiller <julien@lepiller.eu>
Subject: Re: Ideas for ocaml-team
Date: Tue, 20 Jun 2023 08:46:04 +0200	[thread overview]
Message-ID: <ZJFLLGPxRHIQGIHN@Arnaud> (raw)
In-Reply-To: <86bkhgc7jj.fsf@posteo.net>

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

Hi,

Do you plan on including coq.scm in the upgrade plan, as it also depends 
on dune? If so, would coq-packages also be upgraded, or should that be 
done after the ocaml-team branch has been merged with master?

Anyway, I am new to Guix, but will try to help if I can (time- and 
competence-wise) ! :)

-- 
ds-ac

Le Fri, Jun 16, 2023 at 04:32:48AM +0000, pukkamustard a écrit
> 
> Hello Guix,
> 
> I think it's time to start an `ocaml-team` (or `ocaml-updates`) branch
> to collect some bigger updates and changes to the OCaml packages in
> Guix.
> 
> Some things that I can think of:
> 
> * Update OCaml from 4.14.0 to 4.14.1
> 
> * Update OPAM from 2.1.3 to 2.1.5
>   - Requires a major update of ocaml-dose3 from 5.0.1 to 7.0.0
> 
> * Update Dune from 3.6.1 to 3.8.1
> 
> * Update Jane Street packages from 0.15.0 to 0.16.0
> 
> * Remove most ocaml4.07-* and ocaml4.09 packages
>   - We only want to keep the compiler around for bootstrapping purposes.
>   - Update unison 2.51.2 to 2.53.3: This makes it buildable with OCaml
>     4.14 or even 5.0.  (see
>     https://lists.gnu.org/archive/html/guix-devel/2023-02/msg00253.html).
> 
> * Split packages from (gnu packages ocaml) into multiple modules. Maybe
>   in following modules:
> 
>   - (gnu packages ocaml): For the compiler and core dev packages (opam,
>     dune, merlin)
>   - (gnu packages ocaml-boot): For the 4.07 and 4.09 compilers
>   - (gnu packages ocaml-xyz): Everything else
> 
> Thoughts? Any other things? How do we get started with such a branch? 
> 
> Cheers,
> pukkamustard
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-06-20  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16  4:32 Ideas for ocaml-team pukkamustard
2023-06-20  6:46 ` DABY-SEESARAM Arnaud [this message]
2023-06-20 14:31   ` Josselin Poiret
2023-06-21 19:37   ` pukkamustard
2023-06-23 11:48     ` DABY-SEESARAM Arnaud
2023-08-23  8:56 ` Simon Tournier
2023-09-12  6:57   ` pukkamustard
2023-09-12 10:03     ` 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=ZJFLLGPxRHIQGIHN@Arnaud \
    --to=ds-ac@nanein.fr \
    --cc=guix-devel@gnu.org \
    --cc=julien@lepiller.eu \
    --cc=pukkamustard@posteo.net \
    /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).