John Peacock writes:
> C. Michael Pilato wrote:
>> kfogel@collab.net writes:
>>
>>
>>> Couldn't the svn:externals code detect when an external subdir is from
>>> the same repository as its parent, so that
>>
>> It could, but there's reason to assume that just because two projects
> ^no
>> share a repository that they also share the likes of API compatibility
>> and such.
>
> ...
>
>> Rather than introduce conditional behavior, let's keep things simple and
>> educate the users.
>
> Yes, document best practices (using explicit revisions or branches for
> svn:externals) rather than make the code too smart for its own good...
Seems to me that you should always use a tagged (or otherwise
known-not-to-change) external "module" ... this way, your builds of your own
code aren't done against a moving target.
-a
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 28 22:06:21 2005