Hi Russell
> Yes, we use externals for 'proper' externals in another repo, and for
> links to common code in the same repo. For the proper externals, on a
> copy we'd like to be able to have the -r automatically added to the
> external, but with the externals in the same repo, a copy would be
> required.
My take on this is that a local repo should NOT be treated the same as
an external repo. I've seen that consistently in SVN documentation,
there are statements such as copy cannot be across repos, or move cannot
be across repos. I think is a very reasonable limitation. I'd like
svn:externals to stay in the same vein. To truly implement an
svn:externals that works both across repos and locally, what is needed
probably a local abstraction to another repo. With this in place all
other svn operations can be seamlessly done across repos. This should be
long term goal i think. For now, i'd like svn:externals to maintain its
current semantics, which is that it is meant to interconnect 2 different
repos. Please note that this is probably the only component of svn that
interacts with 2 different repos. A exception case really.
To specifically handle the local repo, which is probably more important
than svn:externals, i'd like to have it separate from svn:externals. So
when someday there is a remote repo abstraction, svn:externals becomes a
special case of svn link.
Makes sense?
Thanks
Prasad
Russell Hind wrote:
> Molle Bestefich wrote:
>
>> Narayana Prasad wrote:
>>
>>> But the common code must stay common and
>>> maintain a common history.
>>
>>
>> Except in the case of 'svn cp' to branches or tags.
>> When you branch or tag, you want an actual repository copy of your
>> common files, fixated at the version that is in use when you release
>> (or branch).
>>
>
> Yes, we use externals for 'proper' externals in another repo, and for
> links to common code in the same repo. For the proper externals, on a
> copy we'd like to be able to have the -r automatically added to the
> external, but with the externals in the same repo, a copy would be
> required.
>
> Currently we have to do this manually for all our externals when
> branching for a release which isn't that usable.
>
> Cheers
>
> Russell
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 7 15:49:17 2005