Re: Multiple teams + Different Build Options + One Repository?

Greetings, Shaun Pinney!

> In-Reply-To: <E4A238AC-23F1-4149-9B48-4B506B16A5EE_at_ryandesign.com>
> References: <h88eu1$k8v$1_at_ger.gmane.org> <7e5ba9220909091157r79f3abcdw9fde1b2c8924cd23_at_mail.gmail.com>
> <h8b5f9$n93$2_at_ger.gmane.org> <E4A238AC-23F1-4149-9B48-4B506B16A5EE_at_ryandesign.com>
> Subject: Multiple teams + Different Build Options + One Repository?

First and foremost, please start a new thread by writing a new message instead
of linking deep into unrelated discussion.

> Quick question. We have an SVN repository and are preparing to provide
> access to another development team. An issue which has come up is our
> software has many build options controlled by a few scattered files and each
> team needs different build options. Can we provide both teams a way to
> checkout the latest source code, but with different build options? I think
> we should be able to reduce configuration errors by giving the right build
> options to the right team automatically upon checkout, compared to a manual
> approach of everyone editing on each checkout. Is there a clever solution
> for this (e.g. svn:externals)? Thanks for any advice!

If you need a different building scripts, I think it would be better to
branch them for every team, unless it is possible to maintain a single script
that automatically configure itself for the environment it running in.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 11.09.2009, <5:00>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2393480
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].