On 1/8/2013 11:45 AM, C M wrote:
> All,
>
>
> I am setting up a new repository and have a question on how to handle
> “common” code. Common refers to code which is shared across the multiple
> systems that we deploy.
>
>
>
> In addition to the common code, we also have system-specfic software
> (custom code).
>
>
>
> Given the typical SVN layout, what’s a recommended way to manage this,
> especially when creating release tags?
>
>
>
> In this model, we include the
>
>
>
> /trunk/common_version1/application_1
>
> ../../application_2
>
> ./../application_3
>
>
>
> /trunk/system1/application_1
>
> ../../application_2
>
> ../../application_3
>
>
>
> /tags/system1/Rel_1 [where this may include the system1 apps plus
> common_version1/application_1 and application 3]
>
>
>
> ../system2/application_1
>
> ../system2/application_2
>
> ../system2/application_3
>
>
>
> /tags/system2/Rel_1 [where this may include system2 apps plus
> common_version1/application_1, application_2 and application3]
>
I have similar requirements and have established a layout that works
well for me.
The "common" code exists in a separate repository and I define
references to it where necessary using svn:externals.
When I create a release tag, I use TSVN's nifty ability to peg the
externals at specific revision numbers; this ensures that the tag
contains an exact snapshot of the local ("custom") repository, as well
an exact snapshots of every external.
Does that help?
-Ben
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3041875
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-08 18:59:37 CET