From: Christopher Baines <mail@cbaines.net>
To: Brian Cully <bjc@spork.org>
Cc: 63645@debbugs.gnu.org
Subject: [bug#63645] [PATCH] gnu: swaynotificationcenter: Update to 0.8.0
Date: Mon, 12 Jun 2023 19:38:04 +0100 [thread overview]
Message-ID: <875y7sy17p.fsf@cbaines.net> (raw)
In-Reply-To: <c734e5135bf527b91c800d1296e777615c24ac26.1684765256.git.bjc@spork.org>
[-- Attachment #1: Type: text/plain, Size: 2216 bytes --]
Brian Cully via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/wm.scm (swaynotificationcenter): Update to 0.8.0.
> ---
> gnu/packages/wm.scm | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/gnu/packages/wm.scm b/gnu/packages/wm.scm
> index 4360f3722b..1bf6d46200 100644
> --- a/gnu/packages/wm.scm
> +++ b/gnu/packages/wm.scm
> @@ -147,6 +147,7 @@ (define-module (gnu packages wm)
> #:use-module (gnu packages python-xyz)
> #:use-module (gnu packages readline)
> #:use-module (gnu packages serialization)
> + #:use-module (gnu packages shells)
> #:use-module (gnu packages sphinx)
> #:use-module (gnu packages suckless)
> #:use-module (gnu packages texinfo)
> @@ -1761,7 +1762,7 @@ (define-public swaybg
> (define-public swaynotificationcenter
> (package
> (name "swaynotificationcenter")
> - (version "0.7.3")
> + (version "0.8.0")
> (source (origin
> (method git-fetch)
> (uri (git-reference
> @@ -1769,7 +1770,7 @@ (define-public swaynotificationcenter
> (commit (string-append "v" version))))
> (file-name (git-file-name name version))
> (sha256
> - (base32 "1xvr5m5sqznr3dd512i5pk0d56v7n0ywdcy6rnz85vbf2k7b6kj5"))))
> + (base32 "1c3gd6mlr209jzzrh5jmws2lawnn3gr6smvzcw74kkpi3wvs7l0k"))))
> (build-system meson-build-system)
> (arguments (list #:configure-flags #~(list "-Dsystemd-service=false")))
> (native-inputs
> @@ -1780,11 +1781,15 @@ (define-public swaynotificationcenter
> scdoc
> vala))
> (inputs
> - (list json-glib
> + (list bash-completion
> + fish
> + json-glib
> glib
> gtk+
> gtk-layer-shell
> libhandy
> + libgee
> + pulseaudio
> wayland-protocols))
Hi Brian,
Regarding these new inputs, what's you're reasoning for adding them?
fish stood out to me, it doesn't seem to be referenced by the
swaynotificationcenter output (doesn't show up in guix size), so maybe
it should be a native-input if it's some test dependency?
Thanks,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2023-06-12 18:40 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 [this message]
2023-06-12 19:11 ` Brian Cully via Guix-patches via
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=875y7sy17p.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=63645@debbugs.gnu.org \
--cc=bjc@spork.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).