I work with Subversion and TortoiseSVN GUI. I need to block a repository (making it read-only) so that when I release a version no one can modify that repository. I create a new folder for every version I release.
Asked
Active
Viewed 3,349 times
2
Gilles 'SO- stop being evil'
- 104,111
- 38
- 209
- 254
Matteo Gatto
- 616
- 11
- 28
-
1How is SVN set up? apache2 + dav_svn? – genuineparts Jul 20 '12 at 09:29
-
Do you want to make it read-only AFTER you release? – bahrep Jul 20 '12 at 09:41
-
1Do you want to make repository read-only or a directory inside of it? The latter makes sense, the former is quite unusual. – maxim1000 Jul 20 '12 at 09:56
2 Answers
1
Do you use dedicated Subversion server + Apache2 + ? or work just locally via 'file:///'?
Subversion works with Path-Based Authorization and it's really easy to set authorization rights. BTW if your Subversion server has admin GUI I think the task can be done in a couple of clicks.
bahrep
- 29,961
- 12
- 103
- 150
1
The better way, IMHO, to do that is to :
- allow one person (or group, according to linux permission) to write in /tags path,
- deny to other account (or group) to write there, but give them read permission
- allow writing for everyone in /trunk and /branches.
Then, modify either pre-commit.pl script (see http://ist.berkeley.edu/as-ag/tools/usage/svn-govern-commit-permission.html), or modify access via Apache (here some examples : How to configure SVN web access for different write permissions?).
If you really want to tweak it easy, install a SVN Admin tool : SVN admin management GUI tool
In both cases, you won't be able to set tag in read only mode ... Indeed, you might success writing a perl script, a post-commit HOOK, which will lock the tag, but I'm pretty sure that's a bad idea.
Community
- 1
- 1
Jean-Rémy Revy
- 5,607
- 3
- 39
- 65