A couple high-level questions:
1) there is a need for some server-side tools:
a) create a repository
b) optimize/garbage-collect an existing repository
c) print/purge pending/discarded transactions
I'd like to create subversion/server/ to hold these tools. I'm not sure
if we would have one, or whether we'd have a subcommand like the client.
But the main point is a directory to hold the tool(s).
2) APRUTIL is being put together as a sister project to APR. I'd like to
propose using it for the following features: MD5/SHA1 hashing (MD5 is
currently in APR itself, but it will probably move), some XML utility
functions (and I'd like to shift some of ours over to APRUTIL), the DBM
facilities, and possibly the URI stuff.
The base64 encoding/decoding stuff is there, but it wasn't applicable to
our needs. I'd like to look into resolving some of that (upgrading the
base64 support in APRUTIL and/or shifting some of our support there).
Strictly speaking, our dependency on it would be pretty light.
mod_dav_svn can just use APRUTIL via Apache itself. However, the FS and
the server tool(s) will need MD5 hashing and DBM support (the latter
because mod_dav_svn will use DBM for some stuff, and the tool will need
to deal with those).
[ if Berkeley DB utils were exported from FS, then I'd probably use that;
even better is to add DB3 support to APRUTIL's DBM support. ]
I'm a bit light on rationale for this, but figured it would be good to
bring up now.
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:16 2006