11 messages in com.perforce.perforce-user[p4] Perforce and Seapine Surround SC...
FromSent OnAttachments
Robin Charlton18 Feb 2005 02:07 
Singh, Avichal18 Feb 2005 09:12 
Kyle Turner18 Feb 2005 10:43 
raju...@gmail.com18 Feb 2005 10:48 
hedl...@myob.com22 Feb 2005 16:18 
Dave Rehring22 Feb 2005 16:32 
Smith, Jeremy R (CACI)22 Feb 2005 16:35 
Steve Tapley22 Feb 2005 18:09 
hedl...@myob.com22 Feb 2005 21:01 
Dave Rehring22 Feb 2005 21:14 
Andreas Fischer23 Feb 2005 02:27 
Subject:[p4] Perforce and Seapine Surround SCM compared: any experiences?
From:Andreas Fischer (AndF@orga-systems.com)
Date:02/23/2005 02:27:12 AM
List:com.perforce.perforce-user

perforce-user-bounces at perforce.com wrote on 23.02.2005 06:01:59:

Jeremy and others:

What do you mean by: network enabled client-server architecture, better integration of third-party XML diff tools like

Altova

DiffDog.

These are probably red herrings; they are severe lacks in Visual SourceSafe, not Surround or Perforce. VSS uses network file-sharing and does not have a server app; it relies on file locking.

The biggie for us is that Surround SCM does shares and Perforce doesn't. Think of shares as Windows-type multiple shortcuts in different depots that point to a single file. When you update the file, all the projects/builds in different depots are immediately updated.

Perforce can do this also.

We here do a similar task with a simple script, that assemblies a client spec out of many pieces of parts of the depots.

Every user calls the script to populate his workspace. Now the client spec's sometimes are 20 lines long.

The big advantage is, that we have good control about the changes.

Bye Andreas