You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Gonzalez Diaz, Xoan" <G2...@caixagalicia.es> on 2007/12/13 18:11:11 UTC
File based permissions?
Hi again,
I am setting up a repository of java projects. So my layout is the following:
DEVELOPMENT
APPLICATION
Trunk
src/main/java/es/company/application/component1
es/company/application/component2
...
src/test/java/es/company/application/component1
es/company/application/component2
...
doc/es/company/application/component1
es/company/application/component2
.classpath
.project
Branches
Tags
I want to give read access to all programmers in all directories. And too, read and write access for a programmer modifying a given component in all directories needed, that is:
Src/main/java/es/company/application/component1
Src/test/java/es/company/application/component1
Doc/es/company/application/component1
.classpath
.project
So I define t in access file:
[groups]
es.company.application.component1 = programmer1
[/]
* = r
[Repo:/DEVELOPMENT/APPLICATION/trunk/src/main/java/es/company/application/component1]
es.company.application.component1 = rw
[Repo:/DEVELOPMENT/APPLICATION/trunk/src/test/java/es/company/application/component1]
es.company.application.component1 = rw
[Repo:/DEVELOPMENT/APPLICATION/trunk/doc/es/company/application/component1]
es.company.application.component1 = rw
[Repo:/DEVELOPMENT/APPLICATION/trunk/.project]
es.company.application.component1 = rw
[Repo:/DEVELOPMENT/APPLICATION/trunk/.classpath]
es.company.application.component1 = rw
I want a programmer to be able to modify .project and .classpath but not the other components in trunk different than component1.
When I try to modify .project or .classpath a "403 Forbidden" error is thrown. Isn't possible to define permission over a single file?
Any ideas to achieve this?
Thanks a lot !
Xoan
Xoan González Díaz
Área de Arquitectura EE. FF.
E-mail: g2485 (at) caixagalicia.es <ma...@caixagalicia.es>
xoan.gonzalez (at) tecnocom.es <ma...@tecnocom.es>
Re: File based permissions?
Posted by Andy Levy <an...@gmail.com>.
On Dec 13, 2007 1:11 PM, Gonzalez Diaz, Xoan <G2...@caixagalicia.es> wrote:
> I am setting up a repository of java projects. So my layout is the
> following:
>
>
>
> DEVELOPMENT
>
> APPLICATION
>
> Trunk
>
>
> src/main/java/es/company/application/component1
>
>
> es/company/application/component2
>
> ...
>
>
> src/test/java/es/company/application/component1
>
>
> es/company/application/component2
>
> ...
>
> doc/es/company/application/component1
>
> es/company/application/component2
>
> .classpath
>
> .project
>
> Branches
>
> Tags
>
>
>
>
>
> I want to give read access to all programmers in all directories. And too,
> read and write access for a programmer modifying a given component in all
> directories needed, that is:
>
> Src/main/java/es/company/application/component1
>
> Src/test/java/es/company/application/component1
>
> Doc/es/company/application/component1
>
> .classpath
>
> .project
>
>
>
>
>
>
>
> So I define t in access file:
>
> [groups]
>
> es.company.application.component1 = programmer1
>
>
>
> [/]
>
> * = r
>
>
>
> [Repo:/DEVELOPMENT/APPLICATION/trunk/src/main/java/es/company/application/component1]
>
> es.company.application.component1 = rw
>
>
>
> [Repo:/DEVELOPMENT/APPLICATION/trunk/src/test/java/es/company/application/component1]
>
> es.company.application.component1 = rw
>
>
>
> [Repo:/DEVELOPMENT/APPLICATION/trunk/doc/es/company/application/component1]
>
> es.company.application.component1 = rw
>
>
>
> [Repo:/DEVELOPMENT/APPLICATION/trunk/.project]
>
> es.company.application.component1 = rw
>
>
>
> [Repo:/DEVELOPMENT/APPLICATION/trunk/.classpath]
>
> es.company.application.component1 = rw
>
>
> I want a programmer to be able to modify .project and .classpath but not
> the other components in trunk different than component1.
>
> When I try to modify .project or .classpath a "403 Forbidden" error is
> thrown. Isn't possible to define permission over a single file?
No, it's not (I'm pretty sure the fine manual documents access control
as per-*directory*).
> Any ideas to achieve this?
You could use svnperms.py to provide more fine-grained control on
commit actions. Or, if .project and .classpath are local configuration
information that changes per-developer, tell Subversion to ignore them
outright after removing them from the repository.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org