>
> > What I'd like to do is to ensure that SharedLib, when its
> > checkedout/updated through the svn:externals is marked as readonly.
> > This serves as a reminder to me if I go to edit the project in my
> > TheProduct solution that it should really be modified in the Common
> > solution where I will ensure that it is fully tested,
> documented, etc, etc.
>
> Couldn't this be solved with fine-grained authorization? In
> other words, checkout TheProduct as a particular user, but
> then make sure that same user has no write permission to the
> sharedlibs location?
>
That is one way of doing it, however that same user might be working on
the shared lib but not through an externals link.
I'm not trying to limit peoples access to particular projects, but
rather I'd like to make sure that development is done in the correct
place and not through an svn:external link.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 19 17:03:15 2007