🚀 go-pugleaf

In article <pwolf-2108951700220001@netmgr-807903992.qualcomm.com>, 
pwolf@qualcomm.com says...
>
>In article <8157cb$d3817.364@microforum>, 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
>
>
>I have used a DOS/OS2 only command line driven product called TLIB, 
which
>works well. It keeps the archive in directories and files which mimic
>those in the project
>
>I have also used a product called SOURCESAFE from OneTree which has an 
MS
>Windows interface and also works well. It keeps the archive in a data
>structure which is only accessible by the program. There is, believe it 
or
>not, a MAC version which can share the archive with provision for MAC
>nameing, but the MAC version is command line driven. Microsoft bought
>OneTree recently and I saw a notice that the MAC version was now 
supported
>by someone other than Microsoft.

This isn't quite correct. If you buy SS from MS, you get the DOS, 
Windows, Windows NT and Mac version. The Unix side of SourceSafe is now 
maintained by a third party: MainSoft. These guys have a portability 
layer and tools to compile your Windows apps under Unix. I guess they 
just license the SS source code from MS, and recompile it using their 
tools. 

Greetings, 

Jan Rosseel
A.I. Systems, Belgium.