Ideas for ocaml-team

Ideas for ocaml-team

[pukkamustard]

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

Re: Ideas for ocaml-team

[DABY-SEESARAM Arnaud]

[-- 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 --]

Re: Ideas for ocaml-team

[Josselin Poiret]

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

Hi everyone,

DABY-SEESARAM Arnaud <ds-ac@nanein.fr> writes:

> 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) ! :)

I can also give a hand regarding Coq and libraries, since I have a
vested interest in having everything up-to-date :)

Best,
-- 
Josselin Poiret

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

Re: Ideas for ocaml-team

[pukkamustard]

DABY-SEESARAM Arnaud <ds-ac@nanein.fr> writes:

> [[PGP Signed Part:Undecided]]
> Hi,
>
> Do you plan on including coq.scm in the upgrade plan, as it also depends 
> on dune?

I hadn't thought of the Coq packages, but probably makes sense to update
them together as they will be rebuilt with updates to the OCaml compiler
and Dune.

Do you have an overview of what Coq packages need an update?

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

Yeah, very nice! :) 

-pukkamustard

Re: Ideas for ocaml-team

[DABY-SEESARAM Arnaud]

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

> I hadn't thought of the Coq packages, but probably makes sense to 
> update them together as they will be rebuilt with updates to the OCaml 
> compiler and Dune.
Yes.

> Do you have an overview of what Coq packages need an update?
No, I don't. But there are only a few Coq packages, so I wouldn't mind 
checking every upstream repository.  That said, Coq itself can be 
upgraded.

-- 
ds-ac

Le Wed, Jun 21, 2023 at 07:37:00PM +0000, pukkamustard a écrit
> 
> DABY-SEESARAM Arnaud <ds-ac@nanein.fr> writes:
> 
> > [[PGP Signed Part:Undecided]]
> > Hi,
> >
> > Do you plan on including coq.scm in the upgrade plan, as it also depends 
> > on dune?
> 
> I hadn't thought of the Coq packages, but probably makes sense to update
> them together as they will be rebuilt with updates to the OCaml compiler
> and Dune.
> 
> Do you have an overview of what Coq packages need an update?
> 
> > Anyway, I am new to Guix, but will try to help if I can (time- and 
> > competence-wise) ! :)
> 
> Yeah, very nice! :) 
> 
> -pukkamustard

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

Re: Ideas for ocaml-team

[Simon Tournier]

Hi,

I am very late to the party.

On Fri, 16 Jun 2023 at 04:32, pukkamustard <pukkamustard@posteo.net> wrote:

> 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?


> * 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.

That’s said, aside this bootstrapping consideration, I am in favor to
remove 4.07 and 4.09 OCaml packages.


> * 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

This split makes sense to me.


Do we create the branch ocaml-team for doing this plan?


Cheers,
simon

Re: Ideas for ocaml-team

[pukkamustard]

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

Re: Ideas for ocaml-team

[Julien Lepiller]

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