🚀 go-pugleaf

Paul Groves <paul.groves@oucs.ox.ac.uk> wrote in article
<34438b5e.448185436@news.ox.ac.uk>...
> Has anyone tried using the Windows NT\95 port of GNU RCS?
> ftp://ftp.leo.org/pub/comp/os/os2/leo/devtools/gnu/rcs57pc1.zip 
> 
> First problem I have is that when I checkout (co) a file, it is
> write-protected - is this meant to happen? Surely this is the file you
> want to edit...

co -l checks the file out with a lock so that you can edit it.
The default is without a lock because for most projects it is more common
for you to need to check out a file just for a build and not to edit it. If
you are the only person working on the file than this would be unnecessary,
but if you are not, checking out a file with a lock just to build it would
prevent anyone else in the project from editing it since only one person
can lock a file at a time. Dont change the default unless you are sure that
is what you want.

> Second problem I have that RCS seesm to get files confused with
> directories (or vice-versa?):
> 
> "rlog: f:/Archive/rcs/RCS/index2.html,v: Not a directory"
> 
> I have been trying to use RCS via Emacs 19.34.6 and have already read
> the comments on modifying vc.el in the Win95 Emacs FAQ, but no one
> else seems to mention this problem...Can anyone help?

Hmm how is your build environment set up?
Im guessing that the nonexistant directory is the "RCS" directory and you
are building in the f:/Archive/rcs/ directory. Although I have never used
the win95 version of RCS, the standard UNIX implementation expects the *,v
files to be in a directory called ./RCS which is most often a link to
another directory somewhere in the file system. I am not sure what the
win95 version does since win95 doesnt really have symbolic links, but I'll
bet your problem has something to do with an incorrect path to your *,v
files.