Re: How should I deal with this CVS to Subversion migration issue (and how is this done the Subversion way?)

We just stopped putting the common projects inside of the projects
that share them - the developers just check out the common project as
project 1, and check out their project as project 2 - project 2 simply
references project 1 where it needs to. The build scripts just use
relative paths to jump up one extra folder when they go looking for
the common code.

Externals proved useless for us, because they break when you branch or
tag. Now, if they would implement externals that allowed relative
paths, we would have something that we could work with. But that
hasn't happened yet, as far as I know.

Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 5 17:32:56 2007