Martin Stettner wrote:
> I have a suggestion for the svn client which would IMHO make
> project/tag/branch management a little more comfortable. One could define a
> (client side) project configuration file which defines shorthands for
> Subversion URLS along with standard trunc/tag/branch paths. It could look
> like
> ------------------------
> [project1]
> URL = svn://myhost/some/path
> default = trunc
> tags = tags
> branches = branches
> -------------------------
>
> Using this file, the svn tool could easily do some URL rewrites such as
>
> svn co project1 instead of svn co
> svn://myhost/some/path/trunc project1
> svn co project1/somedir instead of svn co
> svn://myhost/some/path/trunc/somedir project1/somedir
> svn co project1##sometag instead of svn co
> svn://myhost/some/path/tags/sometag project1
Interesting, but I'd disagree. My personal taste is that the svn client should
remain as simple as possible/useful. One reason is that it pins others to
_your_ prj/branch/tag style of doing things.
However, consider a SVN shell like this:
#!/bin/sh
repo = ""
while read cmd args; do
case cmd in
cd)
# change dir
cd args
;;
co)
# checkout
svn co repo$args
;;
co)
# checkin
svn ci repo$args
;;
open)
# set repository URL
repo = args
;;
esac
done
I used something like that for Debian's apt-get/apt-cache and found it quite
useful. Also, it extends without intruding into existing programs, which is a
Good Thing(tm).
Uli
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 5 15:00:24 2004