>> Have you guys given a thought to producing a front end to the admin
commands?
>No. Have you?
Yes, but I don't know the SVN APIs anywhere near enough to do something
about it. You guys do...
>> Like something that will wrap the horrendous dump and filter
interactions?
>Dump/filter/load is a fairly horrendous thing to do to a
>repository, and should not be attempted unless you really know
>what you are doing.
This is why you want to HELP people to do it safely if they need to. For
example - removing a 200Meg file that you've inadvertantly put into the
repository... If you let people do it themselves they can screw things up,
if you automate it and package it nicely people will be able to use it.
> We don't want to make it look easier than it really is and cause people to
trash their repositories.
Look, the process is easy and I have done it myself many times. Alas - I did
it through the CLI which I hate with passion. There's nothing complex about
dumping, running the dump through a bunch of filters and recreating the db
from the filetered dump. The problem is identifying the various elements
that you want to work on. Imagine, for example, that you build an UI to
remove files from the repository. If you build a tool that lets people build
a list of files that they want to be excluded from the repository and then
dump and apply the list on the dump, you are making life safer for people -
YOU have to do it once, properly, and others will use what you worked on.
The major tool needed to handle the admin work is already here - it's the
repo browser, used all over the place to identify files and revisions.
To an extent the admin functions are not unlike the merge operations in that
they are not easy - difficult to do correctly, but with a great UI they
become much clearer for the user.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Aug 22 00:54:11 2005