From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: wayland-compositors: use elogind
Date: Thu, 23 Apr 2020 22:21:56 +0200 [thread overview]
Message-ID: <20200423202156.MpxjCmpXPbxZgVenLnMIWaCZXiqpfiUXROVw7hObocE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21233@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/21233#issuecomment-618645476
Comment:
> Dbus/polkit integration: polkit literally depends on a javascript interpreter and people striving for a KISS desktop don't need these
I think D-Bus is ok, it adds a lot of value, at least from my experience. Polkit I agree has a lot of architectural issues, which is why I only enabled it when I was trying to get flatpak to work.
> Xorg is still root by default on Void
This is, of course, something we can try to change.
> multi-seat, which 95% of people don't use
Good point.
> Logind is more LOC than sway+wlroots combined
Fork elogind and remove multi-seat implementation? Not kidding, I'd be very interested in knowing about a small program for the elogind functionality we need (and if that's even possible). I know ConsoleKit2 was a part of that, but it's unmaintained and seemed quite large still.
> setuid on a local machine is less of a concern than say running a public web server locally or using ssh agent forwarding.
I don't know how to make this judgment. If it's determined not to be a huge risk, I don't have any issue with removing `elogind` as the default option. I mostly want Wayland compositors to have uniform templates.
next prev parent reply other threads:[~2020-04-23 20:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 2:44 [PR PATCH] " travankor
2020-04-22 17:25 ` ericonr
2020-04-23 1:12 ` ericonr
2020-04-23 1:12 ` ericonr
2020-04-23 7:08 ` travankor
2020-04-23 7:09 ` travankor
2020-04-23 7:10 ` travankor
2020-04-23 20:21 ` ericonr [this message]
2020-04-23 20:22 ` ericonr
2020-04-24 6:59 ` travankor
2020-04-25 18:22 ` ShinyRice
2020-04-25 18:23 ` ShinyRice
2020-04-25 19:43 ` hippi777
2020-04-25 19:48 ` hippi777
2020-04-27 14:44 ` ericonr
2020-04-27 20:56 ` [PR PATCH] [Updated] " travankor
2020-04-27 20:57 ` travankor
2020-05-06 4:04 ` ericonr
2020-05-06 8:44 ` travankor
2020-05-06 8:47 ` travankor
2020-05-06 8:47 ` travankor
2020-05-06 8:49 ` travankor
2020-05-06 12:35 ` [PR PATCH] [Updated] " travankor
2020-05-06 19:15 ` ericonr
2020-05-06 21:51 ` ericonr
2020-05-28 21:08 ` ericonr
2020-05-29 7:30 ` travankor
2020-05-30 19:23 ` [nomerge] " ericonr
2020-05-31 18:36 ` travankor
2020-05-31 18:51 ` travankor
2020-05-31 21:29 ` ericonr
2020-05-31 21:30 ` ericonr
2020-08-04 20:30 ` ericonr
2020-08-14 2:31 ` travankor
2020-08-14 2:31 ` [PR PATCH] [Closed]: " travankor
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=20200423202156.MpxjCmpXPbxZgVenLnMIWaCZXiqpfiUXROVw7hObocE@z \
--to=ericonr@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).