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

[Bryan Donlan <bd...@fushizen.net>]

Hi all,

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.

Thanks,

Bryan Donlan

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

[Karl Fogel <kf...@red-bean.com>]

Bryan Donlan <bd...@fushizen.net> writes:
> Hm, I suppose I could go with that. It seems kind of like a hack though:)
> I suppose that for any arguments for a stable-ish (or indeed, unstable
> but supported) out-of-tree fs library API to be really convincing there
> needs to be an actual example of such first :)
>
> I'll go with that initially I guess.

Thanks.  It is sort of a hack, but so is installing a header file for an
unstable API that we're supposedly not publishing :-).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

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

[Bryan Donlan <bd...@fushizen.net>]

On Mon, Mar 31, 2008 at 01:55:00AM -0400, Karl Fogel wrote:
> Bryan Donlan <bd...@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?

Hm, I suppose I could go with that. It seems kind of like a hack though:)
I suppose that for any arguments for a stable-ish (or indeed, unstable
but supported) out-of-tree fs library API to be really convincing there
needs to be an actual example of such first :)

I'll go with that initially I guess.

Thanks,

Bryan

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

[Karl Fogel <kf...@red-bean.com>]

Bryan Donlan <bd...@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.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org