unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 38160@debbugs.gnu.org
Subject: [bug#38160] GNOME Keyring service
Date: Sun, 08 Dec 2019 15:21:24 +0100	[thread overview]
Message-ID: <87y2vmq4nv.fsf@gnu.org> (raw)
In-Reply-To: <2dae337c6b7970b2ec809d98a02c87908a5dd1aa.camel@student.tugraz.at> (Leo Prikler's message of "Wed, 04 Dec 2019 18:50:10 +0100")

Hi Leo,

Leo Prikler <leo.prikler@student.tugraz.at> skribis:

[...]

>> BTW, do you think ‘gnome-service-type’ should always enable
>> ‘gnome-keyring-service-type’?  I would think it’s a good idea.
>> 
>> Thoughts?
>> 
>> Ludo’.
> I'm not too sure about that, to be honest.
> 1. Using GNOME does not imply using its Keyring.  I personally have one
> Guix machine, which just uses GNOME to launch some games, and I could
> imagine some Guix folks do the same with Emacs.  
> 2. The default configuration is made so that it works with GDM, which
> is reasonable, as that is the default for Guix as well.  However, it
> would be possible to launch GNOME from other DMs, which would need
> different configuration.
> Of course, since the service itself is rather small, it would likely
> just "do nothing" for both groups.  However, I would still prefer the
> explicit composition of services over an implicit one – unless a "GNOME
> with GDM and everything else" service was to be added to Guix. 
> Alternatively, we could define a variable %gnome-desktop-services,
> which extends %desktop-services with GNOME, this service, and some
> other GNOME-related services, e.g. one for evolution-data-server.

OK.  I don’t use GNOME myself but I think the goal is for
‘gnome-service-type’ and ‘%desktop-services’ to provide something that
works out of the box, and that’s why I thought it might make sense to
have the keyring service as a default.

But anyway, I understand what you’re saying, so we can leave it as is
and we can always revisit it later if someone feels a need.

Thanks!

Ludo’.

PS: Please keep the bug Cc’d.

      parent reply	other threads:[~2019-12-08 14:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-10 13:06 [bug#38160] GNOME Keyring service Leo Prikler
2019-12-04 17:02 ` bug#38160: " Ludovic Courtès
2019-12-04 17:04 ` [bug#38160] " Ludovic Courtès
     [not found]   ` <2dae337c6b7970b2ec809d98a02c87908a5dd1aa.camel@student.tugraz.at>
2019-12-08 14:21     ` 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2vmq4nv.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=38160@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).