On Tuesday, November 26, 2002, at 12:29 AM, Kent Karlsson wrote:
> How about putting scripts in ~/.subversion/aliases that will be run
> given all the options. Then pretty much anything would be possible.
The downside I see with that solution is it requires scripts in the
directory to have a certain amount of smarts regarding the working copy
and the argument parsing that my solution puts into svn itself so the
scripts don't have to do it. (e.g. "tag=$SVN! $-* cp $REPOS/trunk
$REPOS/tags/$1" doesn't take any scripting.) It also allowed the
calling of arbitrary scripts (e.g.
"tag=$HOME/.svn/aliases/svn-build-tag.pl $**"). However, one might
argue that level of parsing and script calling doesn't belong in svn
anyway. Or there might be a way to get svn to pass all the info to the
script that it would have had available doing alias expansion in my
proposal. What do you think?
On the other hand, I don't see any reason why the two solutions
couldn't coexist peacefully. Probably we should implement the
easier-to-build one first, and see if it meets most people's needs.
Then implement the harder one later if needed. (That's my XP
background talking...)
> As it is right now I already use a couple of extra scripts, but it
> would be nice to run svn buildtag
> instead of svn-build-tag.pl
I agree!
> -- kent
-David Mankin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 26 09:51:10 2002