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

Re: SWIG and platform-specific auth providers (Was: Python bindings build seems broken)

From: Joe Swatosh <joe.swatosh_at_gmail.com>
Date: Wed, 5 Nov 2008 15:19:00 -0800

On Tue, Nov 4, 2008 at 8:39 AM, Jeremy Whitlock <jcscoobyrs_at_gmail.com> wrote:
>> Thanks for the link. I reread that thread and it sounds great to not
>> have to platform specific APIs exposed, but don't we have to support
>> the existing interfaces until 2.0? I look forward to your seeing
>> refactoring.
> Yes but we don't have to expose them to the bindings. Honestly, they
> have never been explicitly exposed before so we are not losing any
> pre-existing functionality.


D:\SVN\src-release-1.5.x\subversion\bindings\swig\ruby>ruby -rsvn\core
-e "puts Svn::Core::VERSION"
1.5.3 (dev build)

test\test_client.rb -v -n"/simp|win|auth|prov/"
Loaded suite test_client.rb
test_add_providers(SvnClientTest): .
test_authentication(SvnClientTest): .
test_simple_provider(SvnClientTest): .
test_username_provider(SvnClientTest): .
test_windows_simple_provider(SvnClientTest): .

Finished in 18.53 seconds.

5 tests, 13 assertions, 0 failures, 0 errors


Those tests are why I came up with the patch in the first place.
While I've never used them, I think they have been "explicitly exposed."

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-06 00:19:10 CET

This is an archived mail posted to the Subversion Dev mailing list.

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