From: Beman Dawes (bdawes_at_[hidden])
Date: 2003-08-06 10:45:29
At 07:58 AM 8/6/2003, John Maddock wrote:
>> Fixed now. I wonder if it really ought to be checked in as binary so
>> this doesn't happen?
>Personally I think that would cause even more problems (for me at least),
>note that there are plenty of other files that need the \r's stripping in
>order for them to work on Unix, in fact some pre-processors (some
>of gcc for example) can't even cope with \r's in header files (if there's
>\r between a \ and a \n).
>The only complete solution is to make sure that all text files have their
>\r's stripped before producing the tar.gz file.
>[ footnote - one way to do this is with the new bcp tool - something
>bcp --boost=boost-path --unix-lines --cvs "." destination-path
>will produce a clean copy of all of the boost cvs with \r's stripped from
>text files - we could probably even write a Jamfile that would automate
>release process come to that. -- end footnote ]
The way we've been doing it for releases is to do a CVS export with the
option for Unix line endings. Once we started with that approach, the
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk