From: muradm <mail@muradm.net>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: control@debbugs.gnu.org, 56094@debbugs.gnu.org
Subject: [bug#56094] [PATCH v2] gnu: wm: Switch sway from elogind to basu.
Date: Wed, 22 Jun 2022 12:38:01 +0300 [thread overview]
Message-ID: <871qvhc9yk.fsf@muradm.net> (raw)
In-Reply-To: <7f0ede4db5c5039dbd0b456435eccd1cbd5bc5f1.camel@ist.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 890 bytes --]
Next one reflecting changes.
Yes, necessary to state basu explicitly, meson.build detects
like systemd -> elogind -> basu. While removed from sway
dependencies, elogind still comes from dependencies of
dependencies.
--
muradm
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
> block 56094 by 56136
> thanks
>
> Am Mittwoch, dem 22.06.2022 um 12:27 +0300 schrieb muradm:
>> * gnu/packages/wm.scm (basu): Switch sway from elogind to basu.
> Should be sway.
>> [inputs]: Replace elogind with basu for sd-bus library
>> dependency.
> This can be simplified to "Replace ‘elogind’ with ‘basu’."
>> [arguments]: Use G-expressions.
> Actually, you don't, and even if, that ought to be a separate
> commit.
>> <#:configure-flags>: Request building against basu.
> Is this necessary? Doesn't sway have autodetection for basu?
>
>
> Cheers
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-06-22 9:41 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 [this message]
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
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=871qvhc9yk.fsf@muradm.net \
--to=mail@muradm.net \
--cc=56094@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
/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).