unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "(" <paren@disroot.org>, muradm <mail@muradm.net>, 56859@debbugs.gnu.org
Subject: [bug#56859] [PATCH] gnu: xdg-desktop-portal-wlr: Change elogind to basu for sd-bus.
Date: Mon, 1 Aug 2022 01:13:18 +0200	[thread overview]
Message-ID: <d2847cba-f3a0-d2b6-3d1d-05dd6a1e0048@telenet.be> (raw)
In-Reply-To: <CLU65BQO1IBU.2P89UAVO6ITXE@guix-aspire>


[-- Attachment #1.1.1: Type: text/plain, Size: 826 bytes --]


On 31-07-2022 23:45, ( wrote:
> On Sun Jul 31, 2022 at 6:38 PM BST, Maxime Devos wrote:
>> What's the reason for the switch?
> Fewer dependencies (we include only the sd-bus library without the whole
> of elogind), and it means eventually desktop users won't ever need elogind
> to even exist in their store. (I think this is the reason. I'm not certain,
> and there may be something more important, like some incompatibility with
> seatd.)
>
>      -- (

That's interesting but sounds very non-specific to 
xdg-desktop-portal-wlr; I think this would be better to propose on 
guix-devel@ to switch elogind->basu for _all_ dependents, not only 
xdg-desktop-portal-wlr -- the latter would increate the closure, not 
reduce it, because other installed packages would still use elogind.

Greetings,
Maxime.


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2022-07-31 23:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31 15:50 [bug#56859] [PATCH] gnu: xdg-desktop-portal-wlr: Change elogind to basu for sd-bus muradm
2022-07-31 17:38 ` Maxime Devos
2022-07-31 21:45   ` ( via Guix-patches via
2022-07-31 23:13     ` Maxime Devos [this message]
2022-07-31 23:32       ` Maxime Devos
2022-08-01  4:55         ` muradm
2022-08-01  5:35           ` [bug#56859] [PATCH v2] " muradm

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=d2847cba-f3a0-d2b6-3d1d-05dd6a1e0048@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56859@debbugs.gnu.org \
    --cc=mail@muradm.net \
    --cc=paren@disroot.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).