[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: converting from SVN to CVS

From: Spiro Trikaliotis <usenet-200901_at_spiro.trikaliotis.net>
Date: Thu, 29 Jan 2009 09:42:00 +0100


Erik Huelsmann wrote:

> On Wed, Jan 28, 2009 at 2:54 PM, Spiro Trikaliotis wrote:
>> Subversion does not trust the OS, but believes to know better - which
>> sometimes results in catastrophic results.
> Cygwin is not an OS. It will never be an OS.

Cygwin is the runtime environment. Yes, it is not the OS itself, but who
is working on the OS itself, anyway? Thus, from the applications point
of view, the runtime environment *is* the OS, although technically not

But I can replace the word OS with runtime environment, if you like, and
restate what I have written.

> 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.

> To adjust
> Subversion's behaviour would be stacking troubles onto troubles.
> Cygwin is the *only* environment which has issues with our handling of
> eols, which - given the number of supported platforms - should tell
> you something.

Yes. We ignore good programming practice (runtime environment that it
knows its environment) and get by on all but one platform. Who is at
fault here? Of course, it's the one platform. Makes sense.

Where is the problem to use (the equivalent of) fopen(..., "rt") (or
similar) in case of text files? Where does it stack trouble onto

> Also: using Subversion on Cygwin (the cygwin version) is an insult to
> the amount of trouble the developers went through to bring to you a
> native Windows version of the tool.

If the native SVN would work flawlessly on Cygwin (in a bash shell), I
would use it. In fact, on one machine, I had tested this. However, there
are problems in this setup, too. For example, SVN cannot call (Cygwin's)
vim in a way that I can enter anything into it for commits, and I do not
like calling svn commit --file XXX to do a commit.

For some multi-platform projects, it is essential for me to be able to
script the automation process as much as possible. That's one of the
reasons why I am using Cygwin, to have a compatible environment. It's
only SVN which causes me problems. Should tell you something. (SCNR)

> BTW: If you have issues with eol handling: just disable it. Subversion
> will leave your files alone and you'll need to configure your editor
> to handle the eols correctly. From personal experience: that works
> great.

Does it work great when working on mixed projects? Remember, I need
CR/LF endings on Windows, but LF endings on Linux and BSD.


Spiro R. Trikaliotis                              http://opencbm.sf.net/
http://www.trikaliotis.net/                     http://www.viceteam.org/
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-29 13:40:33 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.