Re: File based permissions?

On Dec 14, 2007 2:49 AM, Gonzalez Diaz, Xoan <G2485@caixagalicia.es> wrote:
> Oops, it seems a problem to me!
> .classpath and .project are global to all developers, so we could not
> ignore them. One of developers modifying a component could change them
> (i.e a reference or something like that).

You're missing the use case where each developer may need their own
settings in that file.
http://subversion.tigris.org/faq.html#ignore-commit

> I dont't know if svnperms.py could specifiy per-file permission,

Either it or commit-access-control.pl can.

> the problem is that we are automating all the process of giving
> permissions, and this could be achieved in a simple way by only
> modifying snv access file.

Except that the SVN access control file features don't handle individual files.

> If we have now to integrate it with another tool would be a pain!!

I think you should look at the "other tool" before you decide that
it's going to be a pain. Don't you agree that *not* having this tool
is also causing you pain, because you don't have control on these
files?

> I suppose we could modify slightly our layout and make a directory with
> .project and .classpath inside ...
>
> Any other suggestions?

> > -----Mensaje original-----
> > De: Andy Levy [mailto:andy.levy@gmail.com]
> > Enviado el: jueves, 13 de diciembre de 2007 20:37
> > Para: Gonzalez Diaz, Xoan
> > CC: users@subversion.tigris.org
> > Asunto: Re: File based permissions?
>
> >
> > On Dec 13, 2007 1:11 PM, Gonzalez Diaz, Xoan <G2485@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/applicatio
> n/
> > component1]
> > >
> > > es.company.application.component1 = rw
> > >
> > >
> > >
> > >
> >
> [Repo:/DEVELOPMENT/APPLICATION/trunk/src/test/java/es/company/applicatio
> n/
> > component1]
> > >
> > > es.company.application.component1 = rw
> > >
> > >
> > >
> > >
> >
> [Repo:/DEVELOPMENT/APPLICATION/trunk/doc/es/company/application/componen
> t1
> > ]
> > >
> > > 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
Received on Fri Dec 14 14:28:43 2007