mbox series

[bug#66000,0/1] update dune to 3.10

Message ID cover.1694787299.git.benjamin@uvy.fr
Headers show
Series update dune to 3.10 | expand

Message

Benjamin Sept. 15, 2023, 2:20 p.m. UTC 
Hello,

This patch update dune to version 3.10.

This will allow me to push a series of patch to bump eio to 0.12 (as it
depends on dune 3.9 [0]

I check the build of affected packages by running `guix build` on `guix
refresh -l dune`

By doing so, I discovered that it is not possible to build current coq
version with latest dune. That is the reason why I kept the current
version of dune for those packages.

[0] https://github.com/ocaml-multicore/eio/blob/v0.12/dune-project#L1


Benjamin (1):
  gnu: dune-bootstrap: Update to 3.10.0.

 gnu/packages/coq.scm   |  3 +++
 gnu/packages/ocaml.scm | 31 +++++++++++++++++++++++--------
 2 files changed, 26 insertions(+), 8 deletions(-)


base-commit: 69580997bd1b383659b990a5e1e46817e371fa8c

Comments

pukkamustard Sept. 15, 2023, 2:25 p.m. UTC | #1 
Hi,

There's a patch series to update the OCaml compiler, dune and the Coq
clique here:

https://issues.guix.gnu.org/64249

Maybe we can close this issue for #64249?

Benjamin <benjamin@uvy.fr> writes:

> This will allow me to push a series of patch to bump eio to 0.12 (as it
> depends on dune 3.9 [0]

Nice, looking forward to the patches.

Regards,
pukkamustard
Benjamin Sept. 15, 2023, 3:54 p.m. UTC | #2 
Hi

> There's a patch series to update the OCaml compiler, dune and the Coq
> clique here:
>
> https://issues.guix.gnu.org/64249
>
> Maybe we can close this issue for #64249?

Oh I looked for dune open issues but did not find that one.
Sure we can merge it and close this issue
Simon Tournier Sept. 15, 2023, 4:49 p.m. UTC | #3 
Hi,

On Fri, 15 Sep 2023 at 17:54, "Benjamin" <benjamin@uvy.fr> wrote:

>> There's a patch series to update the OCaml compiler, dune and the Coq
>> clique here:
>>
>> https://issues.guix.gnu.org/64249
>>
>> Maybe we can close this issue for #64249?
>
> Oh I looked for dune open issues but did not find that one.
> Sure we can merge it and close this issue

I am closing #66000… nice id number btw. ;-)

Cheers,
simon