[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Unfriendly GNOME keyring prompt

From: Mark Phippard <markphip_at_gmail.com>
Date: Mon, 17 Nov 2014 09:13:17 -0500

On Mon, Nov 17, 2014 at 8:25 AM, Fitzpatrick, Ben <
ben.fitzpatrick_at_metoffice.gov.uk> wrote:

> If you have a default (or blank) Subversion 1.8 ~/.subversion/config and
> use Subclipse with JavaHL, you'll get prompted on startup of Eclipse to
> 'allow Subclipse to remove the current password-stores value from the
> configuration file' (because GNOME keyring password storage doesn't work
> with JavaHL).
>
> If you click 'OK', the config file will contain a line that reads:
>
> password-stores =
>
> which is a blank value, disabling *all* proper password storage services,
> not just GNOME keyring.
>
> This is not very friendly and means that services that work fine (e.g.
> gpg-agent) can't be used without tweaking the configuration back. It also
> messes with other subversion clients which can use GNOME keyring without
> any problems.
>
> Should the default behaviour of the prompt be changed so that it allows
> the other services to be used? Should it automatically use a different
> configuration directory (
> http://permalink.gmane.org/gmane.comp.version-control.subversion.subclipse.user/16665)
> and dump the changed config there?

If you have the option in the config file without gnome-keyring included it
will not prompt you and you also have the option in the Eclipse preferences
of overriding the path to the file so that it leaves the default
~/.subversion path alone.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3091419
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2014-11-17 15:13:23 CET

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.