From: Antero Mejr <mail@antr.me>
To: Arnaud Daby-Seesaram <ds-ac@nanein.fr>
Cc: pukkamustard@posteo.net, 75368@debbugs.gnu.org, julien@lepiller.eu
Subject: [bug#75368] [PATCH] gnu: coq: Update to 8.20.0.
Date: Thu, 09 Jan 2025 16:27:44 -0500 [thread overview]
Message-ID: <87cygv65kf.fsf@antr.me> (raw)
In-Reply-To: <87msg0s4z7.fsf@nanein.fr> (Arnaud Daby-Seesaram's message of "Thu, 09 Jan 2025 10:37:16 +0100")
Arnaud Daby-Seesaram <ds-ac@nanein.fr> writes:
> Thank you for your patch. I have not had the time to look at it in
> detail yet, but here are a few questions/remarks that probably call for
> a V2:
>
> - some Coq-dependent packages are broken by the update (e.g. stdpp needs
> to be updated to 1.11.0 to compile). It would be nice to update
> dependent packages if they support 8.20.
Yes, definitely.
Lately I've been wondering if a coq-build-system would be helpful, since
it seems there's a lot of commonality/boilerplate in the coq- packages.
> - If all Coq packages are updated to support 8.20 (I do not know if it
> is possible), would it be worth renaming Coq into Rocq[0]?
AFAIK the rename is planned for the 9.0 release, which is still another
release away (after 8.21). The rename is going to be a mess. It appears
that the packaging system will be changing again, and also we'll have to
deprecate all the coq- packages if we want to maintain naming
consistency.
> - I understand the addition of python in the inputs, as Coq uses python
> scripts. However, I do not understand why rsync is added as an input.
> Could you say a few words about this?
One of the test scripts uses rsync instead of mv to move a file. I chose
to add the dependency instead of patching it out. Maybe submitting a
patch upstream to fix that would be better.
Thanks for the review!
prev parent reply other threads:[~2025-01-09 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-05 0:55 [bug#75368] [PATCH] gnu: coq: Update to 8.20.0 Antero Mejr
2025-01-09 9:37 ` Arnaud Daby-Seesaram via Guix-patches via
2025-01-09 21:27 ` Antero Mejr [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=87cygv65kf.fsf@antr.me \
--to=mail@antr.me \
--cc=75368@debbugs.gnu.org \
--cc=ds-ac@nanein.fr \
--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).