[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Thomas Hemmer <themmer_at_go-engineering.de>
Date: 2006-12-19 10:59:09 CET

Bill,

I personally would prefer a structure like

/project.root
  /branches
  /tags
    /1.0
      /app1
      /app2
      /common
    /1.1
      /app1
      /app2
      /common
    ...
  /trunk
    /app1
    /app2
    /Common

assuming your app1, app2, ..., appN together form one deployable
product.

Another scenario could be that app1, app2, ..., appN each are separate
products; in this case I would propose the following scheme:

/project.root
  /branches
  /tags
    /app1
      /1.0
        /app
        /common
      /1.1
        /app
        /common
      ...
    /app2
      /1.0
        /app
        /common
      /1.1
        /app
        /common
      ...
  /trunk
    /app1
    /app2
    /Common

Nevertheless I am curious about other ideas that anyone else might have
out there ;-)

Best regards,

Thomas

> -----Original Message-----
> From: news [mailto:news@sea.gmane.org] On Behalf Of Bill Mill
> Sent: Monday, December 18, 2006 11:51 PM
> To: users@subversion.tigris.org
> Subject: 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
>
>
>

---------------------------------------------------------------------
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:08:24 2006

This is an archived mail posted to the Subversion Users mailing list.