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: Fri, 23 Jun 2023 13:48:29 +0200 [thread overview]
Message-ID: <ZJWGjfeO08jmqi73@Arnaud> (raw)
In-Reply-To: <86o7l8r4dy.fsf@posteo.net>
[-- 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 --]
next prev parent reply other threads:[~2023-06-25 8:48 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZJWGjfeO08jmqi73@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.