Reedick, Andrew schrieb:
>> -----Original Message-----
>> From: Joachim Armbruster [mailto:joachima1_at_gmx.de]
>> Sent: Sunday, February 17, 2008 5:03 AM
>> To: users_at_subversion.tigris.org
>> Subject: Migration from Clearcase to SVN / organizing projects
>>
>>
>> We have on a typical file tree structure like the linux kernel source
>> about 200-300 variants, one for each customer.
>> Basically we maintain it that we have a label (tag) for the base
>> platform. Because each customer gets for example a own user interface,
>> we have customer labels as well.
>> Now, it is quite easy in clearcase to have a config_spec which
>>
> contains
>
>> the base label and the customer label. Since the customer label has a
>> higher priority than the base label it accumulates all customer files.
>>
>
>
> This sounds additive and/or an overwrite. No merging is needed?
>
Some merging is needed as well, but should not be the majority of all
the files.
>
>
>
> I'm assuming that your config spec for a 2.0 release for Widgets Inc.
> would look like:
> element * CUSTOMER_WIDGETS_INC
> element * REL2.0_BASELINE
>
> or
> mkbranch rel2.0_widgets_inc
> element * CUSTOMER_WIDGETS_INC
> element * REL2.0_BASELINE
>
> If it's the former (no -mkbranch rule) then you should be able use
> svn:externals to combine the two filesets.
We use the first CC strathegy to include the corrosponding labels.
> Or just have your build or
> packaging scripts copy/tar/add the customer files over the baseline
> files:
> Svn co rel2.0 workspace
> svn export /customer/$CUSTOMER /tmp/build.$$
> cp -pr /tmp/build.$$ workspace
> cd workspace
> make
> cd ..
> tar rel2.0_$CUSTOMER.tar ...
>
>
>
The CUSTOMER_WIDGETS_INC label can "delete" files, does the shown script
the same?
As I recently discovered, some of our project make files just draw all
*.c files... Arghl.
--
mit freundlichen Grüßen,
Joachim Armbruster
Received on 2008-02-20 19:00:57 CET