Re: let's kill svn:externals

----- Original Message -----
From: "Garrett Rooney" <rooneg@electricjellyfish.net>

> ok, that's it, i've seen yet another post by someone with a problem with
> externals, and i've had it. i've been thinking about this for a while,
> and i'm tired of keeping quiet about it.
>
> can we just get rid of the svn:externals feature?

No, please not!

> it doesn't work that well, smacks of 'creeping featuritis', and can
> easily be replicated by a script of some sort for those who need this
> kind of functionality.

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.

> 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?

Stefan

---------------------------------------------------------------------
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:41:36 2003