Go to the previous, next section.

Some questions for people more experiences with CVS.

CVS handled binary files but it seems to corrupt them once and while?

• CVS uses RCS and RCS looks for certain sequences of characters like \$Id\$ and replaces them with version information. So what if a keyword sequence just happens to occur in a binary file since any sequence of ASCII characters is possible? CVS will update any keyword sequences it finds and will corrupt any binary files in which these sequences occur.

  So keyword substitution must be prevented in binary files by added info to the rcs files for each binary file. I also prevent it in any files in which I don't plan to insert rcs keywords just to reduce checkout time. This can be done in the repository using the rcs command:

  rcs -ko <filenames,v>
  

• It might also be because someone is using RCS version 4.x which can't handle binary files. It will corrupt the history files! For this reason it may be necessary to install CVS with a full path to the RCS and diff programs so that it doesn't depend on $PATH which of them are run.

How can I use the \$Log\$ keyword with CVS with Objective-C and // comments?

• RCS (and therefore CVS) doesn't know about Objective-C "//" comments by default. I must inform RCS so that when it expands its \$Log\$ keyword, it will prepend the proper comment characters.

  rcs -c"// " <filenames,v>
  

Go to the previous, next section.