On Fri, Apr 17, 2009 at 9:34 AM, Senthil Kumaran S <senthil_at_collab.net> wrote:
> Neels Janosch Hofmeyr wrote:
>> If I were using some graphical frontend, the textmode-prompt would probably
>> be invisible and things would appear to lock up.
>
> In case of GUI frontend clients, they need to set
> "SVN_AUTH_PARAM_GNOME_KEYRING_UNLOCK_PROMPT_FUNC" to a prompt function which
> will prompt for the default gnome keyring password. If it gets one then gnome
> keyring is unlocked and passwords are stored, if not then simply move to the
> next provider.
>
> The above constant is set as follows in our command line client:
>
> <snip>
> #ifdef SVN_HAVE_GNOME_KEYRING
> svn_auth_set_parameter(*ab, SVN_AUTH_PARAM_GNOME_KEYRING_UNLOCK_PROMPT_FUNC,
> &svn_cmdline__auth_gnome_keyring_unlock_prompt);
> #endif /* SVN_HAVE_GNOME_KEYRING */
> </snip>
>
> The above is the problem faced in subclipse, since in our java bindings we
> don't provide a prompt function for the above value, it tries to open the GNOME
> dialog box for getting the password for default keyring which fails!
Before we "broke" this what would happen is that the GUI that GNOME
provides would come up. We added the code to unlock the keyring in
the CLI environment so that we could support users that are running
without a GUI or X available. But it seems like when those things are
available, the native GUI that GNOME provides ought to still be used.
When this feature was first added and I tested it in Subclipse, that
is how it worked.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1768020
Received on 2009-04-17 15:40:49 CEST