Re: Making file immutable in working copy
From: David Weintraub <qazwart_at_gmail.com>
Date: Thu, 25 Sep 2008 15:18:04 -0400
There are a whole slew of pre-commit hooks that can do just this. In
The most common one is written in Python, and there's an older Perl
Both hooks will allow you to lock a specific file, specific directory,
That way, you can have two people work on one project, but not allow
Take a look at <http://subversion.tigris.org/tools_contrib.html#hook_scripts>
The two you're looking at are:
commit-access-control.pl (and commit-access-control.cfg.examples)
-- David Weintraub qazwart_at_gmail.com On Thu, Sep 25, 2008 at 3:13 PM, Lasse Kliemann <lasse-subversion-users-2004_at_plastictree.net> wrote: > How do I make a versioned file in a working copy immutable, i.e., > prevent it from being changed (especially from being deleted) by > subsequent 'svn up' operations? > > Removing the write permissions in the file system is not > sufficient. One could use 'chattr +i ...', but that involves > superuser privileges (or special capability settings). There must > be a simpler way. > > Rationale: I know that one can always get an old version of the > file from the repository. However, I am concerned with the case > when the server holding the repository is compromised. Yes, then > I play in a backup. However, my users want to be as independent > as possible from any centralized solution; they want to rely on > certain files never changing in their working copies, at least > not without their explicit consent. > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org For additional commands, e-mail: users-help_at_subversion.tigris.orgReceived on 2008-09-25 21:18:30 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.