Re: [boost] Binary files in CVS

From: Michael van der Westhuizen (michael_at_[hidden])
Date: 2005-03-27 12:56:05

Hi Peter,

On Mar 27, 2005, at 4:49 PM, Peter Dimov wrote:

> The following files in the main CVS are binary but do not appear to be 
> marked as such:
>
> M libs/program_options/test/ucs2.txt
> M libs/program_options/test/utf8.txt
> M libs/ptr_container/doc/cboost.gif
>
> The sandbox CVS also contains such files:
>
> M boost/ptr_container/ptr_container.tgz
> M libs/numeric/bindings/doc/c++boost.gif
> M libs/ptr_container/doc/cboost.gif
> M libs/sequence_algo/doc/cboost.gif
>
> These are corrupted by the Windows CVS clients on every checkout via 
> CR insertion. The easiest way to avoid this is to just not check in 
> binary files in the CVS.

That's a bit drastic. The files should be added using a -kb argument, 
as follows:
  cvs add -kb filename.txt

This will avoid keyword expansion.

To recover files already in trouble, do this:
(on a UNIX system)
cvs admin -kb filename.txt
cvs update -A filename.txt
(on a windows system)
cvs admin -kb filename.txt
-- copy a known-good copy of the file over the original
cvs commit -m "fixed binary file" filename.txt

Why does this happen? UNIX systems do not differentiate between text 
and binary
files, and treat everything as text - the CVS behaviour is part of this 
legacy.

Hope this helps...

Michael

> --
> Peter Dimov
> http://www.pdimov.com
> _______________________________________________
> Unsubscribe & other changes: 
> http://lists.boost.org/mailman/listinfo.cgi/boost
>