[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

introduction, and some comments

From: Rob Clark <robdclark_at_mac.com>
Date: 2002-12-27 03:42:46 CET

Hi All,

I've been been keeping an eye subversion for about six months now. Now
I'm in the process of setting up and evaluating svn for a little
project of mine (http://objectscript.sourceforge.net), as a possible
replacement for prcs. The fact that svn uses webdav between client and
server is a very nice feature for me, since I sometimes need to be able
to access my repository from work, where our only access to the outside
world is through a http proxy.

After a couple days of trying to get it to build and run (mostly my
fault... turns out the problems I was having were mostly due to still
having a pre-macosx-v10.2 developer tools installed... but binaries of
the svn snapshot in .pkg form would have made me a very happy camper),
I finally have things up and running. So far I am pretty happy. Other
than lacking merge history, which I think I can get by without for now,
I have a few comments/ideas/suggesions:

"populate"
----------

it would be nice to have a command to automatically add/remove files
that have been added/removed since the last checkout/update, like with
prcs's populate. Perhaps file properties on the directory could be
used to specify a list of regexps to ignore, ie. *.o/*.class/*~/etc.
It seems like this could be done all on the client side. I'll probably
end up doing this with a shell script, but it would be nice to have it
built into the client, since windows users would otherwise need to
install cygwin to use a shell script. I am willing to do some hacking
and send a patch for the "populate" feature, if you think it would be a
good thing to have.

keywords
--------

 From looking through the mailing list archives, this has come up
before. Having per-file keywords is fine, and I will be using them for
sure, but it will be a step backwards from prcs to not have per-project
(per-repository) keywords, at least when I export a release. I think a
compromise solution would be a way to have an export-hook script which
would run on the server when a client is doing an export... if that
export script was able to modify the files sent to the client, then I
could implement my own keyword substitution.

I am not sure if export is a client side only thing, or not... if it is
client side only, then maybe I could do the same thing with a checkout
hook that did the keyword substitution, and perhaps a commit hook that
undid the substitution.

keywords 2
----------

a $Format: "some string"$ keyword, which replaces the following line
with the specified string with all keywords expanded... for example,
with prcs I use something like:

<!--$Format: "<a
href=\"oscript-$ProjectVersion$.tar.gz\">oscript-
$ProjectVersion$.tar.gz</a>"$-->

in the web page, to automatically update the link to the current
version whenever I do a release. I suppose I could achieve the same
thing with a variation of all the keywords that entirely replace
themselves with the keyword expansion.

-- Rob

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 27 03:43:27 2002

This is an archived mail posted to the Subversion Dev mailing list.