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

Create a read-only always updated working copy

From: rouble <rouble_at_gmail.com>
Date: Sat, 31 May 2008 12:39:53 -0400

SVN gurus,

I have a tools directory that contains many executable perl scripts:

I wanted to add this to svn, so I did this:
~$ svnadmin create /path/to/svn
~$ svn mkdir file:///path/to/svn/trunk -m "Adding trunk"
~$ svn mkdir file:///path/to/svn/branches -m "Adding branches"
~$ svn mkdir file:///path/to/svn/tags -m "Adding tags"
~$ svn mkdir file:///path/to/svn/trunk/tools -m "Adding tools"
~$ svn import /path/to/tools/ file:///path/to/svn/trunk/tools -m
"Initial import"

Now, I have /path/to/tools in my svn repository. So far so good.

Now, I want to pull a read-only always updated working copy in
/path/to/tools. So, users can still cd into /path/to/tools and execute
the perl scripts just like they used to. But users should not be able
to edit any of these files in that working copy.

Also, whenever someone commits something to the repository, I want
/path/to/tools to get automatically updated; so users of the scripts
always have the latest version.

I saw that there is a svnsync tool in svn 1.4+, that can help me
achieve what I want, but we only have svn 1.3.2 installed on our
machines here... and there is no plan of an upgrade anytime soon. Is
there another way to do what I want to do?


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-31 18:40:13 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.