Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!labrea!aurora!ames!sdcsvax!ucbvax!decvax!ima!johnl
From: johnl@ima.ISC.COM (John R. Levine)
Newsgroups: comp.sys.ibm.pc
Subject: Re: SCCS for Dos
Message-ID: <690@ima.ISC.COM>
Date: Sat, 22-Aug-87 18:14:04 EDT
Article-I.D.: ima.690
Posted: Sat Aug 22 18:14:04 1987
Date-Received: Sun, 23-Aug-87 13:38:48 EDT
References: <1152@mind.UUCP> <4131@spool.wisc.edu.WISC.EDU>
Reply-To: johnl@ima.UUCP (John R. Levine)
Organization: Not enough to make any difference
Lines: 21
Keywords: software development; source code control; SCCS...
Summary: PVCS from Polytron is much like RCS

In article <4131@spool.wisc.edu.WISC.EDU> jojo@speedy.WISC.EDU (Jon Wesener) writes:
>In article <1152@mind.UUCP> romero@mind.UUCP (Antonio Romero) writes:
>>
>>Anyone know if there's a version of SCCS, RCS, or any other 
>>system for controlling versions of software under development
>>under PC-DOS? ...

I've used PVCS (Polytron Version Control System) from Polytron of Hillsboro
Oregon.  It is much like RCS, to the point of having matching file keywords.
It works pretty well, keeps track of who has what locked in a multiuser
environment, lets you assign version names independently of revision
numbers, can keep a change log, etc.  Costs about $395 for a single
user version, $1000 and up for a network version.

The support is OK, they are interested in hearing about bugs and do
fix them in subsequent releases.
-- 
John R. Levine, Cambridge MA, +1 617 492 3869
{ ihnp4 | decvax | cbosgd | harvard | yale }!ima!johnl, Levine@YALE.something
The Iran-Contra affair:  None of this would have happened if Ronald Reagan
were still alive.