Hey,
>
> * Introduce an svn_fs API (implemented in the loader library) to do
> the translation. I'm a little reluctant to do so at this time
> because it would require building in a little more of the
> FSP-abstraction infrastructure, and as Garrett has pointed out, it
> sucks to have infrastructure with nothing built behind it.
>
>
>
I don't understand how there's "nothing built behind it" if it
facilitates dynamic installation of two existing implementations (Base
and FSFS).
I want to use the svn_config_t structure as the configuration center
piece. The plan was to pass one in on the create call. This has many
long term benefits. Given that the API can't be changed for 1.x,
couldn't we use "repos templates" to install a config file somewhere
beneath the FS base directory and test for it's existence in the create
function and/or loader. If it exists read it and use it to determine
the correct libs and vtables. If it doesn't exist, we install the base
as is. It can be pretty simple for a first cut.
gat
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 28 03:06:43 2004