From: Julien Lepiller <julien@lepiller.eu>
To: Brett Gilio <brettg@gnu.org>
Cc: 38965@debbugs.gnu.org
Subject: [bug#38965] [PATCH 00/12] gnu: coq: Update to 8.10.2.
Date: Mon, 06 Jan 2020 21:34:34 -0500 [thread overview]
Message-ID: <2E36EFCF-C7C0-442B-8F03-46CC3167DA92@lepiller.eu> (raw)
In-Reply-To: <87o8vgm37i.fsf@gnu.org>
Le 6 janvier 2020 21:04:49 GMT-05:00, Brett Gilio <brettg@gnu.org> a écrit :
>Julien Lepiller <julien@lepiller.eu> writes:
>
>> Le 6 janvier 2020 03:24:29 GMT-05:00, Brett Gilio <brettg@gnu.org> a
>écrit :
>>>
>>
>> Looks like lablgtk2 -> ocaml-cairo2 -> lablgtk3 so we can't get rid
>of lablgtk2. Are we sure we need it though?
>>
>> In general, make sure to run guix lint on these patches, I could spot
>missing double spaces in descriptions of the first two for instance.
>
>The OPAM page for cairo2 does not mention needing lablgtk2. So, if that
>is the case I imagine we could be fine deprecating it in favor of
>lablgtk3.
>
>I forgot to lint those who packages, yes. I can change those before
>pushing them. How does everything else look?
The rest looks pretty good :). The introduction of (gnu packages autotools) is too late though, it should be added on the first patch that needs it (5 I think).
next prev parent reply other threads:[~2020-01-07 2:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 8:24 [bug#38965] [PATCH 00/12] gnu: coq: Update to 8.10.2 Brett Gilio
2020-01-06 8:25 ` [bug#38965] [PATCH 01/12] gnu: Add ocaml-cairo2 Brett Gilio
2020-01-06 8:26 ` [bug#38965] [PATCH 02/12] gnu: Add ocaml-lablgtk3 Brett Gilio
2020-01-06 8:26 ` [bug#38965] [PATCH 03/12] gnu: coq: Update to 8.10.2 Brett Gilio
2020-01-06 8:27 ` [bug#38965] [PATCH 04/12] gnu: coq: Reword several comments Brett Gilio
2020-01-06 8:27 ` [bug#38965] [PATCH 05/12] gnu: coq-flocq: Update to 3.2.0 Brett Gilio
2020-01-06 8:27 ` [bug#38965] [PATCH 06/12] gnu: coq-flocq: Use HTTPS home page URI Brett Gilio
2020-01-06 8:27 ` [bug#38965] [PATCH 07/12] gnu: coq-gappa: Update to 1.4.2 Brett Gilio
2020-01-06 8:27 ` [bug#38965] [PATCH 08/12] gnu: coq-gappa: Use HTTPS home page URI Brett Gilio
2020-01-06 8:28 ` [bug#38965] [PATCH 09/12] gnu: coq-coquelicot: Update to 3.0.3 Brett Gilio
2020-01-06 8:28 ` [bug#38965] [PATCH 10/12] gnu: coq-coquelicot: Truncate home-page Brett Gilio
2020-01-06 8:28 ` [bug#38965] [PATCH 11/12] gnu: coq-interval: Update to 3.4.1 Brett Gilio
2020-01-06 8:28 ` [bug#38965] [PATCH 12/12] gnu: coq-equations: Update to 1.2.1 Brett Gilio
2020-01-06 14:00 ` [bug#38965] [PATCH 00/12] gnu: coq: Update to 8.10.2 Julien Lepiller
2020-01-07 2:04 ` Brett Gilio
2020-01-07 2:34 ` Julien Lepiller [this message]
2020-01-07 2:38 ` Brett Gilio
2020-01-07 3:15 ` bug#38965: " Brett Gilio
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=2E36EFCF-C7C0-442B-8F03-46CC3167DA92@lepiller.eu \
--to=julien@lepiller.eu \
--cc=38965@debbugs.gnu.org \
--cc=brettg@gnu.org \
/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).