all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: 35641-done@debbugs.gnu.org
Subject: [bug#35641] [PATCH] services: gdm: Include user profile in D-Bus paths.
Date: Sun, 12 May 2019 23:17:32 +0200	[thread overview]
Message-ID: <87tvdztlsj.fsf@gnu.org> (raw)
In-Reply-To: <87tve051hi.fsf@ngyro.com> (Timothy Sample's message of "Sat, 11 May 2019 13:45:29 -0400")

Hi Timothy,

Timothy Sample <samplet@ngyro.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Timothy Sample <samplet@ngyro.com> skribis:
>>
>> [...]
>>
>>> Is it okay to assume that “.guix-profile” is the user’s profile like
>>> this?  If it isn’t okay in general, is it okay enough for now?
>>
>> In this particular case, I’d say it’s OK.
>>
>> Do we have any other option on the table anyway?
>
> We could run D-Bus from a login shell.  The reason I didn’t opt for this
> is that GDM launches D-Bus from a stripped-down environment.  It’s not
> clear to me if there’s a reason for doing so, or if it was just the way
> the code came together.  Essentially, I’m trying to be conservative.
>
> I’m still holding out hope that a future “user sessions” feature in Guix
> will make all of these hacks go away.  :)

As we accumulate the hacks, motivation rises!  :-)

> I pushed a nicer version (following the style of the “xinitrc” code)
> with a long comment as dcb3a0fe0a086b4762a721e9b1da64826d5160d0.

Thank you!

Ludo’.

      reply	other threads:[~2019-05-12 21:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-08 18:59 [bug#35641] [PATCH] services: gdm: Include user profile in D-Bus paths Timothy Sample
2019-05-10 13:14 ` Ludovic Courtès
2019-05-11 17:45   ` bug#35641: " Timothy Sample
2019-05-12 21:17     ` Ludovic Courtès [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=87tvdztlsj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=35641-done@debbugs.gnu.org \
    --cc=samplet@ngyro.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.