[p4] nothing better about PVCS?

[Raymond Wiker]

Michael Pye writes:
 > I've used PVCS for several years and Perforce for several months
 > and I'd have to say that there just isn't any comparison.  Perforce
 > is in an entirely different class than PVCS.  I'd rather flip
 > burgers for the rest of my life than go back to PVCS.
 > 
 > In addition to simply being an all-around worse tool, the folks at
 > Intersolv (or whoever owns it now) were always great at making lots
 > of promises, but never following up.
 > 
 > Regarding Perforce, the single thing I dislike the most is what
 > seems to be a certain mentality about the way some CM functions
 > should be performed.  For example, there are those who prefer to
 > have a file completely locked when a user does a "checkout" and not
 > allow anyone else to mess with that file until the file is either
 > checked back in or the checkout is cancelled.

	This *is* doable, and has been discussed at length on this
list recently. Hint: "p4 help lock".

 > However, there seems to be an unnatural bias against that method.
 > It's as if someone from on high has declared that not to be the
 > best CM practice, so therefore, Perforce shouldn't support it.
 > There are other examples I've seen discussed here over the last few
 > months (not keeping the original or REAL file- dates is another
 > issue).

	That's also supported, by using the modtimes/nomodtimes option
in the client spec. On the other hand, it *really* makes sense to
let the file timestamp be the time of sync - the alternative is to
*always* do a "make clean" after a sync.

 > I believe this is a very bad approach for Perforce to take.  This
 > is what makes or breaks a product.  If you won't let me do it my
 > way, I'll buy from someone who will.  Translation: If there were
 > another product as good as Perforce, but allowed me more freedom to
 > choose how I wanted to implement CM, I'd be using that instead.
 > But there isn't, so I choose Perforce.

	Your examples are not too convincing :-)

	//Raymond.

-- 
Raymond Wiker, Orion Systems AS
+47 370 61150