public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Tsoy <alexander@tsoy.me>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] State of elogind integration and the default +elogind local USE flag on xorg-server.
Date: Sat, 23 Mar 2019 03:20:26 +0300	[thread overview]
Message-ID: <1553300426.2312.12.camel@tsoy.me> (raw)
In-Reply-To: <20190322235643.2bd9ed7e5a09c7bddac24fca@gentoo.org>

В Пт, 22/03/2019 в 23:56 +0300, Andrew Savchenko пишет:
--------------->%---------------
> > - Making pambase always install the configuration for
> > pam_elogind.so,
> > the same way it does for pam_gnome_keyring.so at this very moment,
> > effectively removing elogind USE flag from it.
> 
> Maybe that's a good time to make USE flag for pam_gnome_keyring.so.
> Really, we shouldn't force users with some crap just "because it
> doesn't hurt (much)".

There used to be a gnome-keyring USE flag that controlled auto-
launching of gnome-keyring-daemon on user login. But now support for
gnome-keyring in pambase is pretty minimal, clearly not deserving a USE
flag:

$ portageq match / pambase 
sys-auth/pambase-20150213-r2
$ portageq contents / sys-auth/pambase-20150213-r2 | xargs grep
gnome_keyring 2>/dev/null
/etc/pam.d/passwd:-password	optional	pam_gnome_keyring.so
use_authtok


  reply	other threads:[~2019-03-23  0:20 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
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 [this message]
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=1553300426.2312.12.camel@tsoy.me \
    --to=alexander@tsoy.me \
    --cc=gentoo-dev@lists.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