From: Brian Cully via Guix-patches via <guix-patches@gnu.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 63645@debbugs.gnu.org
Subject: [bug#63645] [PATCH] gnu: swaynotificationcenter: Update to 0.8.0
Date: Mon, 12 Jun 2023 15:11:38 -0400 [thread overview]
Message-ID: <871qigpk63.fsf@psyduck.jhoto.kublai.com> (raw)
In-Reply-To: <875y7sy17p.fsf@cbaines.net>
Christopher Baines <mail@cbaines.net> writes:
>> (inputs
>> - (list json-glib
>> + (list bash-completion
>> + fish
>> + json-glib
>> glib
>> gtk+
>> gtk-layer-shell
>> libhandy
>> + libgee
>> + pulseaudio
>> wayland-protocols))
>
> Regarding these new inputs, what's you're reasoning for adding
> them?
In general: so that configure would find everything it was looking
for. I believe the only new hard requirement is libgee and
json-glib (I can test a build without them and see how far I get,
but it'll have to wait until I have a bit more time).
The others — bash-completion and fish — are for command
completion, I believe. Do those better belong in native-inputs
just so the can be detected during configure-time?
-bjc
next prev parent reply other threads:[~2023-06-13 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 14:20 [bug#63645] [PATCH] gnu: swaynotificationcenter: Update to 0.8.0 Brian Cully via Guix-patches via
2023-06-12 18:38 ` Christopher Baines
2023-06-12 19:11 ` Brian Cully via Guix-patches via [this message]
2023-06-16 23:12 ` Brian Cully via Guix-patches via
2023-06-16 23:52 ` [bug#63645] [PATCH v2] " Brian Cully via Guix-patches via
2023-06-19 10:14 ` bug#63645: " Christopher Baines
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=871qigpk63.fsf@psyduck.jhoto.kublai.com \
--to=guix-patches@gnu.org \
--cc=63645@debbugs.gnu.org \
--cc=bjc@spork.org \
--cc=mail@cbaines.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).