[ On Tuesday, January 8, 2002 at 19:19:52 (+1000), Nicholas Catanchin wrote: ]
> Subject: RE: Third-party binary files, keyword expansion probs.
>
> So what do I do??
> I'm using CVS v1.11.1p1 compiled for Win32. I don't know whether that is
> POSIX compliant or not? (or what that even means :).
The problems are likely with newlines vs. CRLF. POSIX (IEEE standard
1003.1) probably doesn't really define the line separator character, but
all truly POSIX-compliant systems I know of use only a newline as a line
_separator_ character, and there is no such thing as a "binary" file --
all files are binary transparent, including "text" files.
> I thought that -ko stopped keyword expansion and -kb stopped both
> keyword expansion and newline conversion. Will I lose any functionality
> if I import my text sources into CVS with -kb?? I think that the reason
> the binary files are being corrupted is because of the newline
> conversion.
You really really really really really really should never use CVS for
binary files, especially not when you're using the vendor branch feature
(i.e. "cvs import", esp. more than once). I know I've admitted in the
past to having the odd JPEG and GIF and such files in my vendor-branched
modules, but I'll also note that I've NEVER tried to change such a file
locally, and since I use only unix-type systems I get by just fine with
'-ko' to preserve binary transparency, which of course I want for every
file in such modules, not just the ones which are not normal text files.
--
Greg A. Woods
+1 416 218-0098; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Planix, Inc. <[EMAIL PROTECTED]>; VE3TCP; Secrets of the Weird <[EMAIL PROTECTED]>
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
