From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: muradm <mail@muradm.net>, 56094@debbugs.gnu.org
Subject: [bug#56094] [PATCH v3] gnu: wm: Switch sway from elogind to basu.
Date: Wed, 22 Jun 2022 11:57:17 +0200 [thread overview]
Message-ID: <16e543f33eb1870d0da3a2dbf41e4c2279e4c57d.camel@ist.tugraz.at> (raw)
In-Reply-To: <20220622095249.15421-1-mail@muradm.net>
Am Mittwoch, dem 22.06.2022 um 12:52 +0300 schrieb muradm:
> * gnu/packages/wm.scm (sway): Replace ‘elogind’ with ‘basu’.
> [inputs]: Replace ‘elogind’ with ‘basu’.
Collapse to (sway)[inputs]. No need to repeat yourself.
> [arguments]:
> <#:configure-flags>: Request building against basu.
Since we're at it, this should actually be "Add [the flag]".
> `elogind` still exists as transitive propagated input,
> while `meson.build` auto detects by probing `systemd`,
> `elogind` and `basu` in respective order.
In the source, not in the commit message :P
Can be shortened to "elogind is propagated by [input] and would
otherwise shadow basu".
Cheers
next prev parent reply other threads:[~2022-06-22 10:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 14:39 [bug#56094] [PATCH] gnu: Remove unnecessary sway dependency on elogind muradm
2022-06-20 9:36 ` Liliana Marie Prikler
2022-06-20 10:51 ` muradm
2022-06-21 19:12 ` Liliana Marie Prikler
2022-06-22 9:27 ` muradm
2022-06-22 9:27 ` [bug#56094] [PATCH v2] gnu: wm: Switch sway from elogind to basu muradm
2022-06-22 9:31 ` Liliana Marie Prikler
2022-06-22 9:38 ` muradm
2022-06-22 9:47 ` Liliana Marie Prikler
2022-06-22 9:52 ` [bug#56094] [PATCH v3] " muradm
2022-06-22 9:57 ` Liliana Marie Prikler [this message]
2022-06-22 10:35 ` [bug#56094] [PATCH v4] " muradm
2022-06-22 10:39 ` Liliana Marie Prikler
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=16e543f33eb1870d0da3a2dbf41e4c2279e4c57d.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56094@debbugs.gnu.org \
--cc=mail@muradm.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).