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

Re: Subversion Repository architecture

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-02-27 01:31:29 CET

On Tue, Feb 26, 2002 at 06:06:53PM -0600, SAhmad@oracular.com wrote:
> Hello !!!
> I am a CVS user and was looking at subversion as an option down the line.
> I have some questions about the future direction of subversion:
> - Is the interface to the repository through static function calls or
> through an abstraction layer using shared libraries?
> I would like to have the repository in a database. Best way to get
> there will be to:
> . Implement an interface library to the repository.
> . This library should use dlopen to open a shared library that will
> have the core routines for the repository interface
> This implies that you could have the repository in a database, or
> normal files, or anything else. (Even RCS)
> This feature may make it easier for CVS users to migrate

Please see: http://subversion.tigris.org/servlets/ProjectDocumentList

Read the "Design Document" from that page.

In general, we have a full set of (shared) libraries. Our repository is in a
Berkeley database (which is not replaceable at the moment). CVS repositories
can be converted with the "cvs2svn" tool.

> - Would there be a Visual Studio Plug In?
> - Would there be an Oracle Developer Plug In?

Not unless somebody contributes these, and I haven't heard anybody talk
about it yet.

I highly doubt the Visual Studio plugin will occur. Microsoft is still
working on their third-party plug-in strategy for version control. They used
to publish a thing called SCC API, but they don't anymore (it has been
obsoleted, so they don't want people coding to it).


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:10 2006

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.