jerome jansou wrote:
> Indeed I use the trunc/branches/tags architecture for
> new projects. But my need is more configuration. I
> appreciate the powerfull "copy" fonction, but it
> creates branches, so cannot be use for configuration
> across the branches. I can't flag "i386" a whole
> directory then "ppc" another (like it can be done
> trough properties) and ask something like
> svn checkout svn://host/proj/branches/v1.2 -flag ppc
> to get only the directories/files flagged "ppc" (this
> flag being associated to the directory independently
> of the copies made (or versions)).
> So my only solution is to specify a "view" ppc who
> countains all the leaves files and checkout them
> individually to get my ppc configuration
> Thanks for your time Ryan, I had a way to do it now
> even if it's costly.
Why not create a ppc branch and an i386 branch (customized
appropriately), periodically merge the changes from the trunk into those
branches, and create the appropriate tags from the branches? That way,
you'd have:
-trunk
-branches
-ppc
-i386
-tags
-v1.2
-ppc
-i386
etc. (You could also do dev work in the branches, and periodically
merge back into the trunk; you just need to be careful not to merge back
in the system-specific customizations, or to remove them once they're in
the trunk.) This would enable you to only check out the working
directory you need, rather than the entire repository tree, which would
be good. (Sooner or later, you're going to have enough tags/branches
than checking the entire repository out will completely flood your hard
drive...)
-David
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 20 13:27:30 2005