From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: include dbus session handling in baselayout (or somewhere, in which case where?)
Date: Tue, 7 Jun 2011 23:10:16 -0400 [thread overview]
Message-ID: <201106072310.17515.vapier@gentoo.org> (raw)
In-Reply-To: <BANLkTi=0N1GsFM1B_zJSvigMBLa6C_BRGQ@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1285 bytes --]
On Tuesday, June 07, 2011 22:02:23 Nirbheek Chauhan wrote:
> On Wed, Jun 8, 2011 at 3:41 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Saturday, April 30, 2011 12:20:15 Leho Kraav wrote:
> >> /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.
> >
> > i dont think this makes sense in baselayout. it works great without
> > dbus.
> >
> > doesnt the login manager already take care of launching a dbus-session ?
>
> I believe the use-case is being able to control applications from the
> VTs without having to launch a dbus session manually. Which should be
> done via ~/.bashrc, to be honest. Makes no sense to have a global dbus
> session, since it's supposed to be per-user.
i imagine this could be done via pam too
i dont think this is a global dbus session. it's in profile.d which means it
gets executed at shell login time. i think you meant .bash_login rather than
.bashrc.
probably the only place this could be integrated is in the dbus ebuild itself.
install it as a doc file and elog the info to make the user aware of it. i
don't think this is something we want to install automatically.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-06-08 3:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-30 16:20 [gentoo-dev] Proposal: include dbus session handling in baselayout (or somewhere, in which case where?) Leho Kraav
2011-06-07 22:11 ` Mike Frysinger
2011-06-08 2:02 ` Nirbheek Chauhan
2011-06-08 3:10 ` Mike Frysinger [this message]
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=201106072310.17515.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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