> >
> > 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?
>
> The question is not on the server but on the local machine -
> that is, having the local files being read-only because it is
> from a read-only external.
>
> Thus, this is a client-only type of feature.
>
Exactly, much like the svn:external propery is client-side feature
anyway. It would just be a case of being able to have the svn client
mark the "checked out"/updated files as readonly if the svn:external had
a specific flag attached (not -r as that's already used!).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 19 19:36:38 2007