🚀 go-pugleaf

adrian@microforum.com (Adrian Sampaleanu) wrote:

>I'm investigating version control systems for our medium sized project.  I've 
>used ancient versions of PVCS and MKS RCS.  I have a recent Test Drive version 
>of MKS's Source Integrity.

>Can anyone share their opinions on these and other competing products?  I'd 
>prefer a product with a Win95 style interface.  Source Integrity is close, but 
>it has a few quirks (although my version is from Feb 95, so there might be 
>newer stuff from MKS).

>I'm especially interested to find out about Microsoft's new version control 
>system.

>Thanks in advance,
>Adrian
Well I recently started a project for an NT platform and went with
SourceSafe as our version control system. My first impressions were
rather mixed. The user and administrative interface are fine once you
get the thing setup, but this package is currently ignorant of any
network/groupware issues, which for a source control/configuration
management product is a bit of surprise.

Specifically: there is no network install option or support. Despite
the fact that microsoft will sell you license packs as if you could do
a network install, you can't. Secondly, the software does not
understand UNC pathnames, but requires a (lan) central administrative
directory. Think about it. What we have ended up doing is to have each
engineer do a local install, then blow that away and change the icons
to point to the executibles and directory on our server.  Hello
Microsoft! Anybody HOME? Is everbody busy fixing '95 defects?

That out of the way, I actually like CVS much better, and if there was
an NT gui front end for it I would tend to go that way instead.