Re: converting from SVN to CVS

Hello,

Paul Koning wrote:

>>>>>> "Kenneth" == Kenneth Goldman writes:

> Kenneth> - Newline conversion for Windows is automatic and cannot
> Kenneth> easily be turned off.
>
> I don't understand. If you have an svn:eol-style property it does
> what you ask for (which is vastly superior to what CVS offers).

No, it does not.

In CVS, a svn:eol-style=native file is opened in text mode, leaving the
handling of EOL to the OS (or the runtime environment), "doing just the
right thing".

With SVN, libapr determines an EOL style it believes might be correct,
and the file is written with that.

Unfortunately, libapr is wrong with Cygwin. This is a pity, as it
recognises Cygwin, but it neglects its details. (To be fair: The libapr
API does not have a way to handle this correctly.)

The problem with Cygwin is that there is not one "correct" EOL style,
but two: Cygwin supported LF and CR/LF - and it even supports mixed
configurations, in which some paths are LF, and some are CR/LF. libapr
handles this case statically - it always assumes LF: This is wrong for
many installations.

The easiest correct way: Open the file in text mode and believe the
runtime of Cygwin that it determines the correct style. Unfortunately,
SVN does not believe the runtime, but wants to handle it itself - which
is plain wrong, and a big bug.

CVS does this correctly.

Regards,
Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1055599
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].