From: Leho Kraav <leho@kraav.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Proposal: include dbus session handling in baselayout (or somewhere, in which case where?)
Date: Sat, 30 Apr 2011 19:20:15 +0300 [thread overview]
Message-ID: <4DBC36BF.8050208@kraav.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
Hi all
This is something like net-misc/keychain is for key management. My main
use case so far is to do with gnome-keyring-daemon for Subversion. If
you want to have a password-locked keyring, you will have to unlock it
every time you have a new dbus instance, which can pretty much happen
every time you open a new shell in tmux or whatnot since Subversion
needs dbus to communicate with keyring.
/etc/profile.d/dbus-session.sh attached, looking for feedback about
problems with it and if the whole approach even makes sense. I might be
not knowing something important.
--
Leho Kraav, M.Sc.
[-- Attachment #2: dbus-session.sh --]
[-- Type: application/x-shellscript, Size: 1328 bytes --]
next reply other threads:[~2011-04-30 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 16:20 Leho Kraav [this message]
2011-06-07 22:11 ` [gentoo-dev] Proposal: include dbus session handling in baselayout (or somewhere, in which case where?) Mike Frysinger
2011-06-08 2:02 ` Nirbheek Chauhan
2011-06-08 3:10 ` Mike Frysinger
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=4DBC36BF.8050208@kraav.com \
--to=leho@kraav.com \
--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