From: muradm <mail@muradm.net>
To: guix-devel <guix-devel@gnu.org>
Cc: Maxime Devos <maximedevos@telenet.be>, ( <paren@disroot.org>
Subject: usage of basu as requirement for sd-bus
Date: Tue, 30 Aug 2022 10:59:31 +0300 [thread overview]
Message-ID: <8735dem965.fsf@muradm.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Hello,
basu is sd-bus library extracted from systemd.
Currently, there are two packages depending on it,
which are mako and grimshot.
In https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56859,
I suggest switching xdg-desktop-portal-wlr to basu.
In very same issue, Maxime asks to discuss switching
_all_ dependents of elogind to basu.
[1] Some elogind dependents, like wireplumber, as per
code depends on sd-login.h also in module-logind.c.
While I have wireplumber-without-elogind locally,
I don't propose switching it basu, because someone
may want module-logind.c to work.
[2] Currently there are 1461 packages depend on elogind.
First, all of them should be analyzed if they do use
sd-bus only, those can be switched to basu. Then
those using more than sd-bus should be analyzed if
elogind is missing would their functionality be hurt.
Because of [1] and [2], I find it not feasible/not
possible to blindly switch _all_ dependents from
elogind to basu.
Do I miss anything else here?
Thanks in advance,
muradm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2022-08-30 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 7:59 muradm [this message]
2022-08-30 9:12 ` usage of basu as requirement for sd-bus Maxime Devos
2022-08-30 9:13 ` Maxime Devos
2022-08-30 9:27 ` muradm
2022-08-30 10:03 ` Maxime Devos
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=8735dem965.fsf@muradm.net \
--to=mail@muradm.net \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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.