SteveKing wrote:
> Please define "easily"!
> To get the same functionality with a script would need a huge amount
> of time and maybe it's not even possible. There's no way for a script
> to detect if the property has changed after and update - at least not
> without storing the property value somewhere else too.
I'm not saying it's easy to replicate all of svn:externals, I'm saying
it's easy to replicate the ability to check out other code into your tree.
>>does anyone feel that strongly about keeping it? why? is it just
>>because 'cvs has modules, and this is our equivalent'? if so, that
>
>
> No. I'd like to keep it because it's very usefull if you have several
> library projects which are not stable yet.
> You're asking the wrong question: why does CVS has modules?
I'm not entirely sure. If someone could give me a good explanation, I'd
appreciate it.
It just seems like externals is a poorly thought out feature that
doesn't play nice with a large number of Subversion's subcommands. Some
of these can be fixed, but for some I'm just not sure how to do it (I
can't see, for example, how to update svn:externals entries at branch
time like some people are asking for, at least not without being really
slow and violating many of the nice things about Subversion's branching
style).
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 23 18:47:49 2003