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

Re: Exposing fs-loader.h for out-of-tree filesystem libraries

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Mon, 31 Mar 2008 01:55:00 -0400

Bryan Donlan <bdonlan_at_fushizen.net> writes:
> I've applied to the Git project in google's summer of code to write a
> translation layer which will allow subversion clients to access git
> repositories. I'm planning on implementing this by writing a subversion
> filesystem backend, but I note the fs-loader.h header, containing the
> necessary vtable structure definitions, does not seem to be installed.
> While I understand the fs-loader.h API and ABI should not be considered
> stable across /any/ release rev (even 1.4.x point releases) of subversion,
> would it be possible to add it to the installation under the understanding
> that it is (currently?) an API in flux? This would allow out-of-tree
> filesystem libraries to be created, although they would have to monitor
> changes to fs-loader.h and stay up-to-date when new releases are made.

Personally I'd be uncomfortable adding it to the installation -- but,
you don't really need us to anyway. If you're going to have to track
fs-loader.h closely anyway, then just copy it -- that is, copy the
declarations, and have the copy travel with your sources. You can have
a copy for each official release of Subversion, and choose which one to
used based on autodetection of the exact Subversion version you're
building against.

Would that work?

Good luck with the project, it sounds very interesting.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-31 07:55:13 CEST

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