Tagging With Multiple Projects And One Common Library In The Same Repo

Here's a rough sketch of our repository:

/project.root
  /Apps
    /app1
      /branches
      /tags
      /trunk
    /app2
      /branches
      /tags
      /trunk
  /Common
    /branches
    /tags
    /trunk

ATM, all applications statically compile in the source of "Common", because it's
under very heavy development. (I plan to change this once it stabilizes, but
assume that this is unchangeable for now.)

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 .

Is this the way you would do it? Is there a better way?

You may either assume that repo structure is fixed, or argue that there's a
structure which is *so* better that it justifies the cost of rearranging
everything - both are valid.

The only 2 requirements are that I can
a) build app1/tags/version1 10 months from now, and
b) svn diff app1/tags/version1 app1/tags/version2

Thanks for any ideas,
Bill Mill
bill.mill at gmail.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 19 00:01:15 2006