From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Restructure dependencies on elogind
Date: Sun, 12 Apr 2020 23:58:04 +0200 [thread overview]
Message-ID: <20200412215804.Tks7wC3XggWXhK-j9yOE1hQ6uJF2yIxmz27GmXMEJo8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20930@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
New comment by st3r4g on void-packages repository
https://github.com/void-linux/void-packages/issues/20930#issuecomment-612682196
Comment:
> What other way of setting up `XDG_RUNTIME_DIR` would you suggest?
Well, if you want to follow the XDG spec pedantically there is no simple manual way that I know, because iirc it requires login aware stuff like creating the folder at first user login and deleting it after the last log out. But I don't think this actually matters so much for `libwayland`, it's just a way to have a standard path where to put/discover the socket. It's not even a strict `libwayland` requirement, it's just the only convention used in practice. Maybe someone in the future writes a stripped down elogind-like program that only sets `XDG_RUNTIME_DIR`, idk...
> And Wayland also requires privileges for DRM master
You can actually become DRM master without root privileges, if no one is already master (i.e. you launch from console). But then you can't drop master (don't ask me why... DRM API is like this). So technically it's possible to write such Wayland compositor, but it can't do VT switching.
I don't think adding it to each compositor is a lot of duplication, but anyway just my 2 cents let's see other opinions
next prev parent reply other threads:[~2020-04-12 21:58 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 19:20 [ISSUE] " ericonr
2020-04-12 20:18 ` st3r4g
2020-04-12 20:20 ` st3r4g
2020-04-12 20:30 ` st3r4g
2020-04-12 21:25 ` ericonr
2020-04-12 21:56 ` travankor
2020-04-12 21:57 ` st3r4g
2020-04-12 21:58 ` st3r4g [this message]
2020-04-12 22:08 ` st3r4g
2020-04-12 22:09 ` st3r4g
2020-04-12 22:30 ` st3r4g
2020-04-12 23:28 ` ericonr
2020-04-15 19:33 ` st3r4g
2020-04-15 19:34 ` st3r4g
2020-04-16 12:22 ` travankor
2020-04-16 12:41 ` xtraeme
2020-04-16 13:17 ` travankor
2020-04-16 13:41 ` Duncaen
2020-04-16 13:41 ` st3r4g
2020-04-18 6:47 ` ericonr
2020-04-18 7:49 ` travankor
2020-04-18 7:50 ` travankor
2020-04-18 7:55 ` travankor
2020-04-18 16:20 ` ericonr
2020-04-21 7:44 ` ericonr
2020-04-22 2:45 ` travankor
2020-04-22 14:57 ` travankor
2020-04-22 17:22 ` ericonr
2020-04-22 17:26 ` ericonr
2020-05-30 11:51 ` travankor
2020-05-30 12:52 ` st3r4g
2020-08-14 2:38 ` travankor
2020-12-03 9:52 ` SevereOverfl0w
2020-12-03 11:51 ` st3r4g
2020-12-03 20:49 ` ericonr
2020-12-19 3:30 ` ericonr
2020-12-19 3:30 ` [ISSUE] [CLOSED] " ericonr
2020-12-19 3:31 ` ericonr
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=20200412215804.Tks7wC3XggWXhK-j9yOE1hQ6uJF2yIxmz27GmXMEJo8@z \
--to=st3r4g@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).