🚀 go-pugleaf

I'd be interested in hearing from anybody who has built and used CVS
1.3 on a NeXT, particularly NS2.X (for now).  I'm just starting into
it myself, and have already come up against one bug (NeXT's tmpnam()
doesn't work) and one half-baked CVS command (cvs release just doesn't
seem to work).  I'm wondering what else is in there.  (Yes, I've mailed
info-cvs@prep...)

I was following the NS3.0 nib directory thread that was going a few
weeks ago, and am further wondering if anybody has yet approached
info-cvs people about a way to address this.  It seems clear that the
best way to handle it without a tremendous change to the way CVS keeps
its accounting info, is to move all the CVS/ directories out of the
working source directories into a parallel CVS admin directory tree of
some sort, specified in the environment ($CVSADM?), and defaulting to
~/CVS if no environment value is set.  Comments?
-- 
Royce Howland, DKW Systems Corp.   |  "And since OS/2 2.0 is a 32-bit
       Everything is IMHO          |   operating system, programs are easier
royce@splunge.uucp  (NeXTMail OK)  |   to write and run faster, too."
or kakwa!atlantis!splunge!royce    |  ad for OS/2 2.0