Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bloom-beacon!tut.cis.ohio-state.edu!ucbvax!ucsfcgl!cgl.ucsf.edu!kneller
From: kneller@cgl.ucsf.edu (Don Kneller)
Newsgroups: comp.sys.ibm.pc
Subject: Re: SCCS for MS-DOS?
Keywords: Want recommendations
Message-ID: <11623@cgl.ucsf.EDU>
Date: 25 May 89 20:20:51 GMT
References: <1374@westmark.UUCP> <3952@ima.ima.isc.com> <1506@mtunb.ATT.COM>
Sender: daemon@cgl.ucsf.edu
Reply-To: kneller@socrates.ucsf.edu.UUCP (Don Kneller)
Organization: UCSF Computer Graphics Lab
Lines: 49

In article <1506@mtunb.ATT.COM> dmt@mtunb.UUCP (Dave Tutelman) writes:
>In article <3952@ima.ima.isc.com> johnl@ima.UUCP (John R. Levine) writes:
>>In article <1374@westmark.UUCP> dave@westmark.UUCP (Dave Levenson) writes:
>>>I'm looking for an SCCS-clone for MS-DOS. ...
>>>I use Microsoft C and MASM.  I currently use Microsoft MAKE.  ...
>>
>>I've had good experience with Polytron's PVCS...
>	I, too, have good experience with PVCS. 
>
>>Microsoft "make" is the worst excuse for a make program that I have ever seen.
>	Hear, hear!  It's really a toy.  Get yourself a tool.
>	The MAKE from Turbo C is good, as are Don Kneller's two MAKEs,
>	the shareware NDMAKE and commercial OPUS make.
>
>	HOWEVER... if you use PVCS, it's worth getting PolyMAKE from
>	PolyTron.  It's as good as the others (each has its pros and cons),
>	and it knows about PVCS archives.

OPUS MAKE knows PVCS archives, perhaps better than PolyMAKE does.  This
is because Polytron does not let you know which version it's looked at
when it comes time to check out the file.  So you have to hardcode the
version information in two separate places in your makefile.  This
makes using inference rules involving PVCS files nearly impossible.

For example, with PolyMAKE you might say:
LOGVER	= -r1.1
.LOGFILES: .c_v(.c $(LOGVER))
.c_v.c:
	get $(LOGVER) $<
The problem with using a macro to pass this information is that it does
not work if you need to get a different version for different files.

With OPUS MAKE:
.PVCSLOGFILES: .c_v(.c -r1.1)
.c_v.c:
	get $& $<

where $& is a run-time macro which gets properly bound.

I can give you more information on our product, if you wish.  Look for
our review in July Computer Language.  Hopefully we are the "best buy".

- don

-----
	Don Kneller
UUCP:		...ucbvax!ucsfcgl!kneller
INTERNET:	kneller@cgl.ucsf.edu
BITNET:		kneller@ucsfcgl.BITNET