libsvn_ra is the library for accessing the repository. libsvn_wc is the library for managing your working copy. libsvn_client sits on top of those and provides convenience functionality like checking out and committing to/from a working copy, i.e. the operations typically presented by a user interface.
i am looking into doing internal version managment within a pike process. (ie, not just being a subversion client but maintaining the backend as well with some control over the data storage (like sitebuilder is doing with cvs))
I'm slightly confused. Do you want to implement your own subversion server? From scratch? Or did you intend to use local access with an incompatible backend, thus making interoperability with normal svn clients impossible?
What is the problem you are trying to solve?
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2002-11-12 22:50: Subject: Re: subversion bindings
On Tue, Nov 12, 2002 at 10:25:04PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Bindings for libsvn_client exist, but probably needs some updating to work with the latest beta. Bindings for the other libraries (notably libsvn_ra) don't exist yet.
could you describe what that entails?
i take it that _ra is the serverprotocol library (ra_dav, ra_local and ra_pipe being different methods the server can handle. and that libsvn_client contains what is needed to write a subversion client.
i am looking into doing internal version managment within a pike process. (ie, not just being a subversion client but maintaining the backend as well with some control over the data storage (like sitebuilder is doing with cvs))
so i am mostly interrested in what ever is needed to handle the actual versioning stuff and backend.
greetings, martin.
/ Brevbäraren