[tex-live] svn vs. p4
f.rougon at free.fr
Sun May 21 22:14:25 CEST 2006
Reinhard Kotucha <reinhard.kotucha at web.de> wrote:
> We are using svn+ssh at vntex.org. ssh is the most convenient way to
> access an svn repository especially if you have installed your private
> key. However, we had some problems with group permissions, i.e. some
> files on the server had not been group writable after a commit.
There is a paragraph about that in the svn-buildpackage HowTo
| 2.4 Using by multiple developers
| Multiple developers with local access to the repository may share it
| using a common group. To do so, create a new group and add all
| developers to it. Run "chgrp -R sharedGroup repdir ; chmod -R g+s
| repdir" for the shared group and the repository directory. Now, on
| local access to this repository everybody will create files with the
| appropriate group setting. However, the developers will need to set a
| liberal umask before using svn (like "0022").
| If somebody resists to do so, there is still a brute-force solution:
| fix the permissions with a post-commit script. However, this is an
| "unsound" solution and may lead to ALL KINDS OF PROBLEMS. MAKE SURE
| THAT YOU ARE AWARE OF THE POSSIBLE CONSEQUENCES BEFORE YOU OPEN THE
| PANDORA BOX. See Debian BTS
| [ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=240630 ] for
| details. When you damage your repository, don't blame me and remember
| that there is "svnadmin recover".
| <script snippet to use as post-commit hook>
Maybe that can help...
More information about the tex-live