RE: Readonly externals

>
> Can you give some sort of use-case or rationale for this
> idea? What's the real problem being solved?
>

OK, here's an example:

I have a solution called Common which I use to develop, test and debug a
set of common libraries, for example SharedLib.

I have another solution which I use to develop my product which makes
use of SharedLib. I therefore use svn:externals to add SharedLib to the
source tree and I add SharedLib as a project reference to my solution.

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.

This would also be very useful where the external is pinned to a
specific revision where making modifications makes no real sense.

So, for example, the svn:externals could be:

SharedLib -r 205 -readonly
https://svn.sharedlibs.com/repos/sharedlib/trunk

Or something similar.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 19 11:04:12 2007