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

How to protect an interoffice build-machine from most local changes?

From: x nooby <xnooby_at_yahoo.com>
Date: 2005-10-28 17:35:39 CEST

Is there an easy way to make Subversion emulate the
"lock-edit-unlock" behavior of other version control
systems? My users have a "build-machine" in addition
to their desktops, invariably code changes are made on
this build-machine that are not checked in to the
repository. Is there a way to force someone using
such a public machine to "lock-edit-unlock" files?

Our previous version control system kept files
read-only unless they were "checked out", so you
couldn't modify them without explicitly doing so.
This was a pain on the workstations, but kept the
build-machines from having changes made on them (or at
least many changes made on them).

With subversion, it's easier on the workstations,
because any file can be modified at any time - but it
is also easier for people to make changes on the
public build-machines. This is actually the primary
complaint so far, that it is too easy to make changes.

Is there a preferred solution to this? Policy changes
have not solved the problem.

I didn't want to make the build-machine use an
annonymnous ID with read-only abilities, because
sometimes changes will need to be made on the


Yahoo! FareChase: Search multiple travel sites in one click.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 28 17:39:47 2005

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.