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

Re: Advice on handling common code

From: C M <cmanalyst66_at_gmail.com>
Date: Wed, 9 Jan 2013 09:16:13 -0600

Ben,

Thanks for the reply. I must admit I don't understand the concept behind
"svn:externals" to appreciate how you and others are using it. I need to
read the explanation more carefully.

The option that I can readily relate to is to possibly treat the common
code as a third-party vendor code.

Even then it's unclear how to combine in one release both the common and
the system-system code.

On Tue, Jan 8, 2013 at 11:59 AM, Ben Johnson <ben_at_indietorrent.org> wrote:

> 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].
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3042131

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-01-09 16:16:22 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.