1 |
On Tuesday, June 07, 2011 22:02:23 Nirbheek Chauhan wrote: |
2 |
> On Wed, Jun 8, 2011 at 3:41 AM, Mike Frysinger <vapier@g.o> wrote: |
3 |
> > On Saturday, April 30, 2011 12:20:15 Leho Kraav wrote: |
4 |
> >> /etc/profile.d/dbus-session.sh attached, looking for feedback about |
5 |
> >> problems with it and if the whole approach even makes sense. I might be |
6 |
> >> not knowing something important. |
7 |
> > |
8 |
> > i dont think this makes sense in baselayout. it works great without |
9 |
> > dbus. |
10 |
> > |
11 |
> > doesnt the login manager already take care of launching a dbus-session ? |
12 |
> |
13 |
> I believe the use-case is being able to control applications from the |
14 |
> VTs without having to launch a dbus session manually. Which should be |
15 |
> done via ~/.bashrc, to be honest. Makes no sense to have a global dbus |
16 |
> session, since it's supposed to be per-user. |
17 |
|
18 |
i imagine this could be done via pam too |
19 |
|
20 |
i dont think this is a global dbus session. it's in profile.d which means it |
21 |
gets executed at shell login time. i think you meant .bash_login rather than |
22 |
.bashrc. |
23 |
|
24 |
probably the only place this could be integrated is in the dbus ebuild itself. |
25 |
install it as a doc file and elog the info to make the user aware of it. i |
26 |
don't think this is something we want to install automatically. |
27 |
-mike |