Previously, Ken Schumm wrote in qdn.public.qnx4:
I think I have the latest 4.25 stuff installed, but my ci doesn’t
support the -kb option. I also downloaded the latest rcs archive
from quics, but it’s ci doesn’t support -kb either.
Did you download and port a later version from somewhere?
We use CVS version 1.10, which uses RCS under the hood.
I’m not in fact sure whether CVS 1.10 uses ci and co, or whether the
equivalent functionality is now built directly into cvs. On my
QNX4 machine:
andrew@1:/home/andrew> ci -V
RCS version 5.7
andrew@1:/home/andrew> use ci
ci - check in RCS revisions (UNIX)
…
-k[rev] search for keywords values for revision, etc.
…
This documentation is nonsense. The man page says:
-ko Generate the old keyword string, present in the
working file just before it was checked in. For
example, for the Revision keyword, generate the
string $Revision: 1.1 $ instead of $Revision: 5.13
$ if that is how the string appeared when the file
was checked in. This can be useful for file for-
mats that cannot tolerate any changes to substrings
that happen to take the form of keyword strings.
-kb Generate a binary image of the old keyword string.
This acts like -ko, except it performs all working
file input and output in binary mode. This makes
little difference on Posix and Unix hosts, but on
DOS-like hosts one should use rcs -i -kb to ini-
tialize an RCS file intended to be used for binary
files. Also, on all hosts, rcsmerge(1) normally
refuses to merge files when -kb is in effect.
CVS respects these flags. I’ve never really delved any deeper than to
determine that -kb was necessary for binary files. Since it really
has to do with keyword substitution, you can get lucky with binary
files that happen not to contain the $keyword …$ pattern in them.
This is not normally a good risk.
Cheers,
Andrew