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

> Yes we would expose the new API from the Ruby bindings.
>
> My compatibility concerns arise from your statement that the "the explicit use
> of the platform-specific auth providers in Ruby should be removed." Since we
> put them out there it seems like we have to support them, but I realized as I
> was reviewing your refactoring in the other thread that we could make the Ruby
> bindings support the old APIs through this new interface.

You maintain the bindings right? If I commit the patch, do you mind
exposing the new function, and upgrading the old functions to really
just call the new function behind the scenes? Actually, you take
whatever approach you want. ;)

-- 
Take care,
Jeremy Whitlock
http://www.thoughtspark.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org