> Have you considered the fact that when you branch your top project,
> you not only branch every subproject below it, but also you create a
> new branch of every branch of every subproject, so to speak.
>
> I say down that path lies madness, unless you are very careful what
> should be modified and what shouldn't.
Yeah, it definitely seemed like things would get crazy fast, but it was the
best idea I could come up with to do everything I wanted.
> Instead, have a simple layout where no project is contained inside
> another - and use svn:externals to build up an entire project tree
> from them.
I guess for me the confusion comes in if I need to branch a whole suite of
projects. Let's say that there's a not quite major update going on, but one
that will impact half the projects. If I just take the suite and create a
branch, I now have this separate working version, without having to branch
each individual version. Of course maybe having to manually assemble off of
the externals for a suite release is the price to pay for having some
sanity.
If you have external items referenced, and you branch, do you effectively
branch those externals as well? Or must you go to the real location of the
external, branch it there, and change the external reference?
> Or just have them all inside a single project tree, and
> only use svn switch on the working copies to switch the project
> subtrees on branches as needed.
Can you please explain what you mean here? svn switch just changes the
working copy, and I would have to use that regardless of the approach I took
wouldn't I?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 26 20:06:44 2004