I have two projects in the same repository project A and project B.
They do not have a common parent that I can use to check them both out
in with a single checkout command. Project B depends on A and our
build process checks out both projects, builds A, then builds B.
I was thinking there is a potential race-condition if changes are made
to A that B depends on such that if I check out rev R of A and rev R+1
of B the build will fail.
My first thought was that I could create the illusion that A and B had
a common parent in the repository such that I could get them both with
a single checkout and be sure to get the same revision for each, simply
by using svn:externals to pull them into the same working copy. But
then it occurred to me that since svn:externals is designed so that it
can link to entirely different repositories that a checkout with
multiple svn:externals properties still likely acts as several distinct
checkouts and it is therefore not atomic.
Is this assumption correct? That sv:externals can not be used to group
projects into a single atomic checkout, at least not without resorting
to specifying the exact revision number for each URL in the
svn:externals property?
If so, I think whenever the relative URL for svn:externals issue is
being worked on, that this idea of making the checkout atomic when
possible could be addressed as well.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 26 17:03:54 2005