news <news@sea.gmane.org> wrote on 12/18/2006 02:50:32 PM:
> Here's a rough sketch of our repository:
>
> /project.root
> /Apps
> /app1
> /branches
> /tags
> /trunk
> /app2
> /branches
> /tags
> /trunk
> /Common
> /branches
> /tags
> /trunk
>
><<<snip>>>
>
> The question is, how should I create a Tag for version 1 of app1, such
that it
> includes Common in some way?
>
> After much discussion of svn:externals, various branching schemes, and
other
> weirder ideas, a fellow programmer and I decided that the best answer
was to
> copy the app1 release into app1/tags/version1 , then copy /Common/trunk
into
> app1/tags/version1/commonlib .
>
> <<<snip>>>
This reminds me of the "complex tags" scenario described at
<http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html#svn.branchmerge.tags.mkcomplex>
. You can create a working copy that contains a combination of revisions
(by using `svn update`) and branches (by using `svn switch` on certain
directories). If you can get a working copy to look exactly as you like,
then you can copy the working copy to the appropriate URL on your server.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 19 13:09:32 2006