From: Andreas Sturmlechner <asturm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Piotr Karbowski <slashbeast@gentoo.org>
Subject: Re: [gentoo-dev] State of elogind integration and the default +elogind local USE flag on xorg-server.
Date: Fri, 22 Mar 2019 21:47:07 +0100 [thread overview]
Message-ID: <91370575.RfKHrJFilt@tuxbrain> (raw)
In-Reply-To: <5aa7ae5e-94d8-2428-ccd5-ea4c04ebf5e4@gentoo.org>
Short anwer: Right now, xorg-server[+elogind] is at odds with desktop profile
that still has +consolekit by default.
For good reasons (long answer):
elogind integration tracker not yet done: https://bugs.gentoo.org/599470
bluez hard-requiring systemd with user-session: https://bugs.gentoo.org/639434
Besides the above, have we really identified all packages that need fixing? I
certainly haven't made an attempt.
Here's how these flags relate, and how they should be set globally:
?? ( consolekit elogind systemd )
We know from previous fallout (skypeforlinux) that merely having elogind
installed besides a system built with +consolekit globally will result in
runtime issues.
Therefore, not one single package, unless it hard-depends on exactly-one-of (
elogind systemd ) should enable elogind by default at this time. Doing so now
only makes people switch it off globally either before or after they are facing
runtime issues.
Let's fix the remaining bugs, create a proper news item in advance, and then
switch over desktop profiles to elogind as the new default.
Regards,
Andreas
next prev parent reply other threads:[~2019-03-22 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 20:32 [gentoo-dev] State of elogind integration and the default +elogind local USE flag on xorg-server Piotr Karbowski
2019-03-22 20:43 ` Brian Evans
2019-03-22 20:48 ` Piotr Karbowski
2019-03-22 20:47 ` Andreas Sturmlechner [this message]
2019-03-22 21:07 ` Piotr Karbowski
2019-03-22 21:13 ` Andreas Sturmlechner
2019-03-22 20:56 ` Andrew Savchenko
2019-03-23 0:20 ` Alexander Tsoy
2019-03-22 21:09 ` Roy Bamford
2019-03-22 21:17 ` Michał Górny
2019-03-22 23:30 ` Piotr Karbowski
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=91370575.RfKHrJFilt@tuxbrain \
--to=asturm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=slashbeast@gentoo.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