GNOME Bugzilla – Bug 171399
gnome-keyring-daemon should be installed to libexec
Last modified: 2009-03-01 23:45:43 UTC
gnome-keyring-daemon is a daemon not intended to be run by the user, so it should be installed to libexec and not to bin.
*** Bug 149815 has been marked as a duplicate of this bug. ***
Created attachment 51175 [details] [review] gnome-keyring goes to libexec No changes to gnome-session should be necessary - this should probably be tested though.
Why do you think no changes to gnome-session are needed? Gnome-session tries to find gnome-keyring-daemon in the path at build-time. At the very least you have to rebuild gnome-session (making the patched gnome-keyring incompatible with current gnome-session packages), but even then its unlikely to find gnome-keyring since libexec isn't in the path. Did you try this?
Oh sorry, yes obviously it will be necessary to also patch programs that launch gnome-keyring so it knows to look it libexec. However that should be a trivial change to make. Do you want me to provide you with a patch for gnome-session to fix its configure file to first look for gnome-keyring-daemon in libexec?
What I'm worried about is releasing a new version of gnome-keyring that is totally broken with all previous releases of Gnome. Maybe we should finally sync the gnome-keyring version with gnome, that would make it obvious that you can only use the current gnome-keyring with Gnome 2.13.x. Anyway, could you provide patches for gnome-session too?
Any news on this bug ? somebody works on the patch for gnome-session ?
Also, other apps that launch gnome-keyring, like the pam work needs to be changed.
I am neutral on this subject. I would spend the time to change pam_keyring to look in libexec if that is the overall decision. I will leave this up to the gnome-keyring maintainers, but if it is going to be changed please email me.
The Debian guys seem to dislike libexec: bug #366749
Debian can always configure with --libexecdir=something
Right, and libexec makes more sense than /usr/bin for installing programs that users are never intended to run. It clutters the user's PATH to install things into directories that are in the default PATH when they are programs that are only started programmatically.
BTW, the next version of GNOME Keyring will be 2.19.2 (ie: synced up with GNOME).
Why do you think it's not intendet to be launched by user ? It's a user process, and although there is session auto-launch now there's the possibility, after all, some different session likes to use it, in which case it would be either called by gk-manager or even just inserted into some autostart setup. I launch gkd and gnome-setting-deamon manually, for example. As for 'cluttering' /usr/bin, personally i like to see what's basically available to be a user process, and i guess that's how Debian tends to see it. Is ssh intendet to be launched by a user ? "Yes, sometimes" - here we are.
I think in the common case, it is not intended to be run by the user directly, but instead from various programs. If a user really wants to run such a program directly, putting it in libexec doesn't prevent them from doing so. On Solaris, more effort is placed to move things that are not commonly used by normal users into libexec. I am just requesting that it should be possible to specify the directory where gnome-keyring-daemon is installed when you run configure.
gnome-keyring-daemon is run from all sorts of scripts and strange setups, especially for users of alternate desktops like KDE. These scripts and uses will break if we move it. I personally think it'll be easier to just leave it in bin. Closing this bug, but if that's simply unaceptable please feel free to reopen it.