>I store project's FrameMaker documentation as binary files in
>the CVS-1.9 repository. It is convenient to handle project's docs and
>sources in the same place. For proper handling doc files, I included
>following lines in the `cvswrappers' file:
> # Handle FrameMaker files.
> *.fm -m 'COPY' -k 'o'
>It works OK except that after I have edited some `*.fm' doc file in my
>working directory, and somebody else has committed its own version of
>this file, I can not run `cvs update': my local editions will be lost.
I also know that problem, and we decided, that only one person changes files
of a class. For instance, everybody knows, only person A changes the *.fm-files,
only person B changes *.bin-files in directory xxx, and so on. If person C
want to change *.fm-files, she first informs A to commit his changes, before
C changes them.
Quite silly, I know.
Probably you could use the `cvs watch' / `cvs [un]edit' commands to perform
this `protocol' via cvs itself. See cvc documentation for that. I didn't try
Additionally, probably RCS like file-locking is possible via the `cvs admin'
command. With RCS file locking semantics, only one user at a time should be
able to work on that file. I also didn't try it. Sorry.
If someone tried RCS file locking with CVS, I'm interested in it.
Signature fault (.plan dumped)