Tobias Ringstrom <tori@ringstrom.mine.nu> writes:
> > > There is built-in support. Put something like this in your post-commit
> > > hook.
> > >
> > > #!/bin/sh
> > >
> > > db_archive -a -h /path/to/repo/db | xargs rm
>
> The problem with the current approach is that you have to learn about
> Berkley DB in order to use Subversion. I think that it would be great if
> the user did not *have* to do that. Except for the log file issue the BDB
> is invisible to the user. The log files are the only thing that sticks
> out.
I something think that it's a bummer that we haven't abstracted away
that basic task (database archival/cleanup) like we did with database
recovery (see `svnadmin recover'). But I fear that when there is more
than one database backend for our users to choose from, we'll find
that the semantics of those operations are differ wildly from database
to database, and we'll end up dropping the abstraction altogether.
Ultimately, yes, Subversion requires that you a) know that is uses a
given database backend, and b) know how to maintain that backend. I
don't think it's *really* that terrible of a thing to ask of our
users, though our documentation could be quite a bit more helpful --
and the blame for that falls to me. Sorry.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 4 15:54:00 2003