[p4] Usefulness of "file spec" integrations

[G Barthelemy]

I found one use-case where the Perforce branch spec is very useful and
actually a feature that ClearCase is lacking: when importing third
party code from a supplier, which you need to integrate to your source
tree and develop further, and when both your and the supplier source
trees differ structurally.

Defining a branch spec between a vendor branch (where the vendor code
is imported "as is") and the import branch for your project allows you
to change (remap) the directory structure as you integrate. It becomes
particularly useful when you need to go through that exercise again
with subsequent releases of the supplier code.

-- 
Guillaume

On 9/19/07, David Weintraub <qazwart at gmail.com> wrote:
> I actually think this is one of the weaknesses of Perforce. This
> manual tracking is error prone. You have to remember which branchspec
> was used, to modify the branchspec when you change the directory
> structure, and to make sure the changes you put in the branchspec are
> accurate. It would be nice if Perforce could actually version
> directories.