> > Unless I miss my guess, the Subversion project itself uses this to
> > incorporate some or all of its external library
> requirements (apr, apr-util,
> > neon, etc.)
>
> Well, actually, svn only uses released versions of those libraries;
> we're not interested in tracking the latest versions day-to-day.
>
> And in any case, they don't have svn repositories yet. :-)
>
Well, that's pretty weak of them... why haven't they caught up yet? ;-)
Seriously though, suppose for the sake of discussion that apr, neon, et al.
were indeed using svn as their VCS of choice. I understand that you would
only want to tie in the latest release to which the Subversion code has been
updated (thinking about API shifts and all that, esp. with neon). But could
this not still be done using svn:externals? Couldn't you pin the definition
down to http://project.org/tags/releases/x.y.z ? Or even, if you wanted to
be particularly fascist about it, couldn't you tie it to a specific revision
number with a -r4242?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 28 19:58:41 2004