Re: converting from SVN to CVS

Hello Jeremy (and Toby),

* On Thu, Jan 29, 2009 at 02:02:46PM +0000 JeremyP wrote:
>
> On 29 Jan 2009, at 08:42, Spiro Trikaliotis wrote:
>
>> Hello,
>>
>> Erik Huelsmann wrote:
>>
>>> Cygwin is an ugly
>>> workaround for problems people are having with their OS.
>>
>> Oh, that's the problem: We don't like Windows, thus, we don't like
>> Cygwin, either. Yes, that's easy.
>
> Actually, that's not what he's saying, in fact quite the opposite.

Ok, I might have misunderstood his statement here.

> The issue arises from the fact that Cygwin tools use LF for text file
> end of lines,

No, they do not. With Cygwin, you can configure the line endings you
want to have. On all the machines I have Cygwin installed, Cygwin uses
the CR/LF convention.

> but Windows tools use CR LF. Thus, if you mix Windows and
> Cygwin tools you get into a terrible mess.

Currently, there are exactly three tools that are problematic with CR/LF
endings on Cygwin (on my machine, there might be others):

1. SVN
2. git
3. The installation of the X fonts

For 3., I have a work-around. For 1., the only workaround is to compile
my own version, patching SVN. This only works as long as I do not have
mounted directories that use LF endings, though. Sometimes, I also use
d2u/u2d tools

For 2. my solution is to use a mount which uses LF endings.

> I'd like to blame Subversion for that, but unfortunately, we were
> a CVS shop at the time.

I still blame SVN for this, as I am convinced that the way SVN handles
line endings is flawed.

> You should try TortoiseSVN. Then the editor becomes irrelevant.

I am scripting very much of the process, and these scripts have to run
on Windows, Linux and xBSD. That's why I stay away from GUIs here.
@Toby: Thus, Eclipse + Subclipse is not a solution for me, either.

Regards,
Spiro.

-- 
Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/