Thank you very much for the clear explanation; that helps a lot. For
now, I think I will follow your suggestion of reorganizing the
repository.
Is this issue considered a bug or a mis-feature? Are there any plans
to fix it? I know that Subversion prides itself on cheap copies which
can be used as tags, but it seems like this way of doing things makes
tags basically useless to those without full permissions on the tree.
Thanks again,
-Emin
On Wed, Jun 25, 2008 at 6:53 AM, John Peacock
<john.peacock_at_havurah-software.org> wrote:
> Emin.shopper Martinian.shopper wrote:
>>
>> Is there a way for a user with limited access to trunk (i.e., a user
>> who cannot read certain directories) to make a tag?
>
> Think of it this way: Subversion's security exists in a file outside of
> repository itself, and is strictly path based. If you were allowed to tag a
> directory containing a subtree that you wouldn't have rights to under the
> security stanza, you would suddenly have rights to *all* paths in the tag.
> There is no way to automatically update the security settings in response to
> tagging.
>
> The contrapositive would be even worse: if you allowed someone to make a tag
> of a directory containing prohibited paths, but simply excluded those paths
> from the tag, then you wouldn't have a consistent tree. In addition, a tag
> by someone who lacks some rights would now be different from someone who had
> all rights.
>
> In order to make a tag, you have to have full rights to all directories and
> files below the tagged directory. You will have to restructure your
> repository (or rethink your security), so that prohibitions exists only in
> peers to the trunk, not children.
>
> Sorry
>
> John
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-25 13:35:55 CEST