unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: pukkamustard <pukkamustard@posteo.net>,
	Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Ideas for ocaml-team
Date: Tue, 12 Sep 2023 12:03:12 +0200	[thread overview]
Message-ID: <A573EACB-82E8-4DA0-9C18-63B47D34759A@lepiller.eu> (raw)
In-Reply-To: <86zg1r3m2z.fsf@posteo.net>

I don't think it makes sense to have a separate brarch when we have so few contributions, and so few impacted packages

Le 12 septembre 2023 08:57:56 GMT+02:00, pukkamustard <pukkamustard@posteo.net> a écrit :
>
>Salut!
>
>Simon Tournier <zimon.toutoune@gmail.com> writes:
>
>>> 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.
>>
>> I think that’s a great idea. :-)  Any progress on this?
>>
>
>There is #64249 (https://issues.guix.gnu.org/64249) to which I just
>submitted a v6.
>
>>> * Remove most ocaml4.07-* and ocaml4.09 packages
>>>   - We only want to keep the compiler around for bootstrapping purposes.
>>
>> Currently camlboot is used by ocaml-4.07-boot used by ocaml-4.07.  But
>> then version 4.09 and later and not bootstrapped; well they use the
>> upstream bootstrap (which is boot/ocamlc and friends IIRC).
>>
>> Well, independently of this upgrade plan, the OCaml bootstrap could be
>> the chain 4.07 -> 4.09 -> … and I do not know if 4.09 would be enough
>> for 4.14.  And if 4.14 would also be enough for 5.
>
>I don't know either and I don't think I will have time to look into this
>soonish.
>
>I think placing the 4.07 and 4.09 compiler in (gnu packages ocaml-boot),
>even if unused, seems reasonable. We should add some nice
>comments/breadcrumbs for whoever looks into completing the chain in the
>future.
>
>> That’s said, aside this bootstrapping consideration, I am in favor to
>> remove 4.07 and 4.09 OCaml packages.
>
>Ack
>
>> Do we create the branch ocaml-team for doing this plan?
>
>Just asked a similar question in the cover for the v6 to
>#64249. Basically I don't know how fast I/we will be able to look into
>the other items in this list. Maybe it makes sense to just merge in to
>master instead of having a too long-lived ocaml-team branch? Or set a
>pre-defined time-to-live for the branch? What's the current modus
>operandi for other teams?
>
>Cheers,
>pukkamustard


      reply	other threads:[~2023-09-12 10:31 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
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 [this message]

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=A573EACB-82E8-4DA0-9C18-63B47D34759A@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    --cc=pukkamustard@posteo.net \
    --cc=zimon.toutoune@gmail.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.
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).