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

Re: Ability to make updated files read-only?

From: Andy Levy <andy.levy_at_gmail.com>
Date: 2006-01-24 21:18:14 CET

On 1/24/06, Xn Nooby <xnooby@gmail.com> wrote:
> Is it possible with TortoiseSVN and the normal SVN CLI tools to
> automaitcally make files read-only? If it was just the CLI tool, I could
> use a batch file that did an attrib command, but I don't know how to make
> TortoiseSVN do it. Is there an elegant solution? This is for a "buildbox"
> that users have a tendency to make fixes on, then forget to check them in.
> So we are trying to prevent them from being able to make changes by turning
> on the readonly flag after a checkout or update. This is on a Win 2003
> Server machine.

Are these same developers pulling the updated files from the
repository to the build box? If so, that can make this real tricky -
they need write access to the files to update them. 3 options I can
think of:

1) A scheduled task running under a system account to do an svn update
on a regular basis, then set the read-only attribute. Developers only
allowed to start the build, not do an update (not sure how this would

2) A build tool like Anthill to do a build on a schedule, a la
continuous integration. No developer needs to touch the build tool's
working copy.

3) Change the build script(s) to first run an svn st and if any
add/modify/delete/merge/conflict is found, halt the build so that the
developer can only complete the build if the WC is in sync w/ the

All have pros and cons and for all I know could be about as airtight
as a basketball net.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 24 21:19:45 2006

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.