Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Restructure dependencies on elogind 
Date: Mon, 13 Apr 2020 01:28:38 +0200	[thread overview]
Message-ID: <20200412232838.ik6sSjzRfPRfK3Y-F892BJwgtxzplfzGiqMzJ5DV7G4@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: 580 bytes --]

New comment by ericonr on void-packages repository

https://github.com/void-linux/void-packages/issues/20930#issuecomment-612691870

Comment:
@travankor at least for the sway package, setting setuid for it is determined by the template. Do you mean that Cage has only recently gained the capability of being setuid? Because the package definitely doesn't set it.

@st3r4g I actually really like the idea of adding elogind as a dependency of wlroots. GNOME and KDE already require elogind, so the only compositor that wouldn't require it is weston, AFAIK. Have you ever used it?

  parent reply	other threads:[~2020-04-12 23:28 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
2020-04-12 22:08 ` st3r4g
2020-04-12 22:09 ` st3r4g
2020-04-12 22:30 ` st3r4g
2020-04-12 23:28 ` ericonr [this message]
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=20200412232838.ik6sSjzRfPRfK3Y-F892BJwgtxzplfzGiqMzJ5DV7G4@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).