May have given the wrong impression here - its not access control but just
limiting the depth of checkout to folders matching the list.
On Thursday, 29 March 2012 12:49:57 UTC+1, Nico Kadel-Garcia wrote:
> On Thu, Mar 29, 2012 at 7:19 AM, Paul Coulson <paul_at_coulsonweb.co.uk>wrote:
>> I have a legacy repo structure that has many projects with their own tags
>> and branches folders.
>> Users check out the whole structure as there are common lib references
>> etc, but they don't need to see the full contents
>> of tags or branches folders, which can be massive.
>> I would like a property svn:inhibit (similar to svn:ignore) set on the
>> root folder
>> that limits the checkout depth for a folder anywhere in the tree that
>> matches the inhibit list.
> Woof. From the view of a sophisticated user, I don't think it's
> feasible. Access control is built into daemons, mod_dav_svn, svnserver, and
> file:/// access from the subversion client. Weaving in the ability to
> parse the repository characteristics and restrict access on that basis is
> asking for a signigifcant rewrite of the system, and sounds like a really,
> really, destabilizing idea. It certainly wouldn't backport to older
> Subversion server software.
> You can do some access control with Apache configurations or access.conf,
> but neither of those will restrict file:/// access. I suggest you pick an
> access method to allow, block all others, and rely on the existing
> structures to do that kind of control on the server side.
Received on 2012-03-29 18:51:29 CEST