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
> >
> > $ svn up -rN
> >
> > would update both the parent and the svn:external subdir to N in that
> > case? And in the not-same case, it would update the parent to N and
> > the external to HEAD, as it does now, of course.
>
> It could, but there's reason to assume that just because two projects
> share a repository that they also share the likes of API compatibility
> and such. That is, just because the APR team tweaks some APIs in
> their /trunk doesn't mean that the Apache HTTP Server guys have
> changed HTTP Server to track those API changes yet.
Might be true for the Apache project, but there's just as many
projects where the opposite is true. We have some of those.
> Rather than introduce conditional behavior,
> let's keep things simple and educate the users.
Since everybody's already abusing 'svn:externals', a wiser choice
would be to introduce a 'svn:internals' with the desired behaviour,
eg. one that updates the files like the users are expecting.
Another Good Thing (TM) that this would bring to the table would be
that 'svn cp' could have an option named '--pin-internals' that users
could use when tagging a project, so that shared files remain tagged
(instead of following HEAD ?!).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 7 13:19:52 2005