From: "Ludovic Courtès" <ludo@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: 60386@debbugs.gnu.org
Subject: [bug#60386] [PATCH] gnu: Add guile-proba.
Date: Tue, 10 Jan 2023 11:48:45 +0100 [thread overview]
Message-ID: <87358ioeb6.fsf@gnu.org> (raw)
In-Reply-To: <nSZT0otTqh8SJirEUyeY-gOQrmjfQ5JSbI6MNIKZ0TlzwZ-8Xc0U_ggLZqI_exvM_hYXn5n9On7nl83zToicXU5HLgM8VpAENp0H4zKQ6po=@protonmail.com> (Luis Felipe's message of "Wed, 28 Dec 2022 18:07:52 +0000")
Hello!
Luis Felipe <luis.felipe.la@protonmail.com> skribis:
> From 332ea52f1f060a4fa1b8af7100b4cbd2f481f24b Mon Sep 17 00:00:00 2001
> From: Luis Felipe <luis.felipe.la@protonmail.com>
> Date: Wed, 28 Dec 2022 12:45:32 -0500
> Subject: [PATCH] gnu: Add guile-proba.
>
> * gnu/packages/check.scm (guile-proba): New variable.
[...]
> + (native-inputs (list guile-3.0 texinfo))
> + (propagated-inputs (list guile-3.0 guile-config guile-lib texinfo))
I don’t think ‘guile-3.0’ and ‘texinfo’ need to be propagated, do they?
Apart from that it LGTM, thanks!
Ludo’.
next prev parent reply other threads:[~2023-01-10 10:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 18:07 [bug#60386] [PATCH] gnu: Add guile-proba Luis Felipe via Guix-patches via
2023-01-10 10:48 ` Ludovic Courtès [this message]
2023-01-13 15:41 ` Luis Felipe via Guix-patches via
2023-01-17 13:50 ` Ludovic Courtès
2023-01-18 18:20 ` Luis Felipe via Guix-patches via
2023-01-23 22:25 ` Ludovic Courtès
2023-01-25 1:11 ` Luis Felipe via Guix-patches via
2023-01-26 9:35 ` Ludovic Courtès
2023-01-26 14:29 ` Luis Felipe via Guix-patches via
2023-02-06 15:40 ` Luis Felipe via Guix-patches via
2023-02-13 13:44 ` Jelle Licht
2023-02-15 21:56 ` Luis Felipe via Guix-patches via
2023-02-21 17:54 ` bug#60386: " Jelle Licht
2023-02-15 21:59 ` [bug#60386] [PATCH v4] " sirgazil--- via Guix-patches via
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=87358ioeb6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60386@debbugs.gnu.org \
--cc=luis.felipe.la@protonmail.com \
/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.