Re: Arguments to favor Subversion against Perforce

one of the advantages could be the LDAP authentication mechanism in
Subversion, which will not be supported by Perforce till the next X-Years
:-(

                                                                           
             bse2000@gmx.de
                                                                           
             22.11.2004 23:21 To
                                       users@subversion.tigris.org
                                                                        cc
                                                                           
                                                                   Subject
                                       Arguments to favor Subversion
                                       against Perforce
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           

Hi everyone,

I'm wondering whether you could help me to list arguments against a switch
from Subversion to Perforce (or that would support a switch from Perforce
to
Subversion).

I must admit that I'm quite new to SVN but used CVS and ClearCase at lot
before. Now I started with SVN some weeks ago due to its nice features,
e.g.
to be able to rename and move files, atomic commit and the capability of
differential treatment of binary files. I like SVN because of its easy to
use and intuitive interface.

Due to that we have to use Windows (:-(), I was happy that the nice
TortoiseSVN exists and is relatively stable, so that also the newbees in
our
group could easily start without learning the command line interface.

However, some people in our department use Perforce and our VP asked us to
use only one version control tool :-(

The main intention to use version control in our group is to allow an easy
sync between different sites during hectic projects. We do not really have
huge software development projects. Only some scripts (Perl, Matlab, Batch
files etc), Excel sheets, Word documents and other binary files. So there
is
no real need to do extensive branching or merging.

Our department is distributed all over the World (mainly California and
Germany) using all kind of interconnection interfaces. Hence, we would like
to use version control also when logging remotely into our intranet (e.g.
dialup with wired or wireless phones, WLAN hotspots or hotel internet
connections).

I read an 'old' thread about 'Subversion vs. Perforce' and wonder whether
there are perhaps more arguments I could list in order to stay with
Subversion and to convince Perforce users to switch to it.

Any hints are very much appreciated!!

Best regards
BSE

PS: I need to have at least some arguments until end of this week to bring
them up on a meeting next Monday.

--
Geschenkt: 3 Monate GMX ProMail + 3 Top-Spielfilme auf DVD
++ Jetzt kostenlos testen http://www.gmx.net/de/go/mail ++
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org