We are trying to handle a situation where we have two simulation packages --
call them SIM1 and SIM2. Each of these are set up as separate projects in a
It turns out that SIM1 and SIM2 today have much code that is common or share
functionality and we are attempting to create a common code share in a new
We know that you can use the externals property to set up a checkout of
One problem is the procedure needed to enable the handling of share. I have
the following questions:
1. Changes to SHARE should be controlled for check-in purposes. For example,
can the checkout of share using the externals setting be automated to create
a tag for SHARE as SHARE_SIM1_Rel_s1 so changes to that tag only get checked
into that branch (?) or tag. Similarly for SHARE_SIM2_Rel_s2. That way, when
changes need to be made into the trunk of SHARE, then they can be done
through a formalized merge from the tags to the share.
2. Alternatively, provide some class of users a way to check out read only
versions of SHARE that cannot be checked back into the SHARE project.
I figure someone must have dealt with similar problems before, but I was not
able to find information beyond use of the externals property. I appreciate
any help from folks.
Received on 2009-01-20 23:33:28 CET