[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Readonly externals

From: Michael Sinz <Michael.Sinz_at_sinz.org>
Date: 2007-02-19 19:33:26 CET

Ben Collins-Sussman wrote:
> On 2/19/07, Nick Vaughan <n.vaughan@codestuff.net> wrote:
>
>> 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?

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.

-- 
Michael Sinz                     Technology and Engineering Director/Consultant
"Starting Startups"                                mailto:michael.sinz@sinz.org
My place on the web                            http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
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:34:12 2007

This is an archived mail posted to the Subversion Dev mailing list.