From: Edward Rudd <urkle@outoforder.cc>
To: git@vger.kernel.org
Cc: Eric Wong <normalperson@yhbt.net>
Subject: Re: [git-svn] always prompted for passphrase with subversion 1.6
Date: Tue, 14 Dec 2010 09:33:44 -0500 [thread overview]
Message-ID: <4D078048.3040602@outoforder.cc> (raw)
In-Reply-To: <4AA84F46.6010706@hp.com>
On 09/09/2009 08:58 PM, Tim Potter wrote:
> It's probably just a matter of adding another entry to the
> _auth_providers() function in git-svn. My thought was that there might
> be a new auth provider in the Subversion 1.6 client library for GNOME
> Keyring support that could be used for this.
>
> I'll have a search through and see what I can find.
I've been tracking subversion bug # 3612
(http://subversion.tigris.org/issues/show_bug.cfg?id=3612 ) which is on
this issue of perl binding not supporting platform specific providers.
A patch was added into subversion 1.6.15 that finally adds bindings for
perl to access this functionality via a call to
SVN::Core::auth_get_platform_specific_client_providers and adding it's
contents to the array returned by _auth_providers..
The "test" modification I did to git-svn is as follows.
sub _auth_providers () {
(
SVN::Core::auth_get_platform_specific_client_providers(undef,undef),
[
SVN::Client::get_simple_provider(),
.... the rest of the static provider ...
]
)
}
I'm honestly not sure if it should be at the beginning or end, and this
also needs some run-time checking to determine if the user has at least
SVN 1.6.15 installed
prev parent reply other threads:[~2010-12-14 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 0:38 [git-svn] always prompted for passphrase with subversion 1.6 Tim Potter
2009-09-05 6:46 ` Eric Wong
2009-09-10 0:58 ` Tim Potter
2010-12-14 14:33 ` Edward Rudd [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=4D078048.3040602@outoforder.cc \
--to=urkle@outoforder.cc \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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.
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.