unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: muradm <mail@muradm.net>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 56094@debbugs.gnu.org
Subject: [bug#56094] [PATCH] gnu: Remove unnecessary sway dependency on elogind.
Date: Mon, 20 Jun 2022 13:51:21 +0300	[thread overview]
Message-ID: <87r13jtw6g.fsf@muradm.net> (raw)
In-Reply-To: <aa918162af56ffa9736708d5a76979dd4d463ca6.camel@ist.tugraz.at>

[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]


Hi,

elogind/systemd was used via wlroots actually.
wlroots dropped elogind/system in favour of libseat.
libseat can talk to either systemd, elogind or seatd.
this is already reflected in wlroots package.

setuid thing you point is reflected as warning in meson.build.
there is no functionality behind it as far as I know.
and in 1.7 meson does not look at them directly, but via wlroots.
basically informative from sway point of view.

the only thing left behind is swaybar which relays on
either systemd, elogind or basu for system tray functionality.
this could be used as argument for keeping elogind
as dependency.

you may look at #49969 which added the other day
seatd-service-type and greetd stuff.

--
muradm

Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:

> Hi,
>
> note that "unnecessary" is quite judgmental.  Why is it 
> unnecessary?
> By default, guix tends to include "optional" inputs such as 
> elogind.
>
> Am Sonntag, dem 19.06.2022 um 17:39 +0300 schrieb muradm:
>> * gnu/packages/wm.scm (sway): Cleanup dependencies.
> The ChangeLog should explicitly say what is done, i.e. 
> (sway)[inputs]:
> Remove elogind.
>
>
> What exactly is the goal here?  As far as I'm aware sway works 
> either
> with *logind or seatd or by having itself be setuid.  If the aim 
> is to
> support seatd-based services, I think having a sway-with-seatd 
> variant
> would be better.
>
> WDYT?


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2022-06-20 11:43 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 [this message]
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
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=87r13jtw6g.fsf@muradm.net \
    --to=mail@muradm.net \
    --cc=56094@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).