Scott Palmer wrote:
>
> On 23-Nov-05, at 3:39 AM, allan@muly.dk wrote:
>
>> eh, can you please explain exactly what VSS sharing can do that the
>> svn:externals property can not do more elegantly?
>
>
>
> svn:externals can be much more painful to deal with than VSS sharing.
>
> With svn:externals:
>
> -- the access protocol is hardcoded in the externals definition, so
> even if you get your WC with SVN protocol the external definition
> might have HTTP protocol. This is a problem when using svn: in the
> office and svn+ssh from home for example.
>
> -- updates are not atomic, each svn:externals link is pulled in as a
> separate update request, possibly getting a later revision of the repo.
>
> -- commits don't dive into the svn:externals links at all. (though I
> think tortoisesvn DOES do this)
>
> -- tagging is painful if you wish to tag the svn:externals links with
> the main project branch
>
Hi Scott,
Maybe I'm wrong but it seems to me that using the good practice of
including the revision namber in svn:externals both your point 2 and 4
are solved.
Isn't it?
Maurizio de Pascale
mdepascale@dii.unisi.it
> Some of these things will be solved when relative paths are supported
> for svn:externals (or perhaps "svn:internals", whatever it gets called)
>
> Scott
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 24 14:05:08 2005