Sam Johnston wrote:
> Ben Collins-Sussman wrote:
>
>> Someday an svn repository will correctly interoperate with vanilla DAV
>> clients, i.e. will do 'autoversioning.' I've been working/thinking
>> about it.
>
>
> Hopefully said client(s) will support DeltaV by then too.
>
>> The issue is that VSS, CVS, and DAV-sans-deltaV all share the concept
>> of "per-file" revision numbers, rather than svn's global ones.
>> Someone else on this list expressed frustration when trying to map svn
>> to the VSS api; you might run into the same problems with
>> Macromedia's version-control api, not sure...
>
>
> The API seems fairly simple. There are only a handful of *required*
> commands, most of which are trivial to implement. I wonder if it would
> be worth writing a DLL which simply calls the svn command?
Brrrr, anything but that!
> Ideally there would be a client DLL I could wrap around but from a
> quick glance at the Subversion package installed on my *doze box there
> doesn't appear to be.
Subversion is all about libraries. The command-line client is just a
thin layer on top. You don't see any Subversion DLLs on Windows because
there aren't any -- it's all linked statically at the moment -- but your
DLL could link with the Subversion libs directly. Wrapping around calls
to the command-line client is not only cumbersome, it's also slow.
> I'm a little out of my depth with Win32 development too - I guess this
> is as good a place as any to get up to speed.
By all means, go for it! The command-line client is a reference
implementation; you can find examples of how to do almost anything in there.
--
Brane Čibej <brane_at_xbc.nu> http://www.xbc.nu/brane/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 14 21:23:32 2002