On Tue, Aug 05, 2003 at 03:50:10PM -0500, cmpilato@collab.net wrote:
> Vladimir Berezniker <vmpn@tigris.org> writes:
>
[snip]
> > Is there a particular reason you want a list of only used log files?
>
> Once again, we're running up against a place where a clean API
> contradicts the main use-case. To name a function
> svn_repos_logfiles() implies that those log files are actually
> interesting. It's a weird scenario, if you think about it. We are
> trying to name function which return a list of things we *want*, but
> those things are the names of files that we *don't want*. :-)
>
> You know, I can't bring myself to care about this. Do what you think
> is right.
>
> > Any chance end users might think "lslogs" has something to do with log
> > messages? See above above regarding the "[--ignore-unused]" part.
>
> Yes, good point. "lsdblogs" ?
lsdblogs is OK, I suppose, but the main use-case for this is to remove
the unnecessary Berkeley DB log files. How am I supposed to remove
these files if the svnadmin lsdblogs command gives me all of the logs,
including the ones that are still in use? Oh, that's right, I first run
svnadmin lsdblogs to get all of the logs, then I run svnadmin lsdblogs
--ignore-unused to get the ones that are still in use and compare the
lists to find the ones I can safely delete!
What's the point of that? :)
What would make *much* more sense is for the default to list only the
unused logs and a switch to list all of them. (Which is what Vladimir
was advocating.)
By the way, is svnadmin always only going to operate on Berkeley DB
based Subversion repositories?
--
Michael Wood <mwood@its.uct.ac.za>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 6 17:35:24 2003