Re: svn:eol-style issue

[Barry Scott <ba...@barrys-emacs.org>]

On Oct 30, 2006, at 14:06, Giulio Troccoli wrote:
> Hi everybody,
>
>
>
> I have an issue with the EOL and consequently with the svn:eol- 
> style property. I have found another post about it but it didn’t  
> say how to solve the issue, and also it was a bit old so maybe now  
> we do have a solution.
>
>
>
> The problem is across-platform problem. We have Subversion 1.3  
> installed on a Linux box, but the product is maintained on AIX,  
> Solaris and Windows. All developers use Visual Studio to do their  
> job and TortoiseSVN to commit the changes.
TSVN does not work on AIX or Solaris. How do you checkout the files  
on those systems?
If you use TSVN to checkout onto a network file system that you share  
with AIX then the line endings will be native to windows e.g. CRLF.
>
>
> On AIX and Windows everything is fine, but on Solaris sometimes the  
> build failed because the compiler does not like the EOL of some  
> files. These happens (and strangely not always) when the files have  
> been edited using Visual Studio.
VS is a Windows tool and it only uses CRLF EOL. Don't use it to edit  
unix files and things will work better.
Try using an editor that understands line endings. SciTE or Barry's  
Emacs work with any EOL.

Barry

Re: svn:eol-style issue

[Nikki Locke <in...@trumphurst.com>]

Giulio Troccoli wrote:
> I know that TortoiseSVN does not work on AIX and Solaris, in fact I
> said that they use Visual Studio, which, as long as I know, runs only on
> Windows.
> 
>  
> 
> On Solaris and AIX we just use Subversion to check out the code.
> And this is why I hope I would find a solution to my problem using
> Subversion, 
> instead of, as someone suggested, using a third-party
> editor in Windows.

I use Visual Studio to edit files which also have to compile on Unix.

TortoiseSVN successfully checks out these files to my Windows box, and the 
line endings all come out \r\n (crlf).

The Linux SVN client checks out the same files to the Linux box, and the 
line endings all come out \n (lf only).

The only time I encountered a mixed line endings error message was when i 
used Ankh (the Visual Studio SVN addin) to diff a file, and copied some of 
the text from the repository side of the diff to the working copy side.

I concluded that this was a bug in Ankh (not honouring the eol-style 
property).

So there is something more to your problem than plain use of TortoiseSVN 
and Visual Studio.

Do you share your Windows or Solaris development areas over the network? If 
you used the Solaris SVN tools to check out the files to a shared 
development area (thus making the line endings \n) and then used Visual 
Studio to edit them in that shared area, you would have a problem.

-- 
Nikki Locke, Trumphurst Ltd.      PC & Unix consultancy & programming
http://www.trumphurst.com/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: svn:eol-style issue

[Giulio Troccoli <Gi...@uk.linedata.com>]

Barry,

 

I know that TortoiseSVN does not work on AIX and Solaris, in fact I said
that they use Visual Studio, which, as long as I know, runs only on
Windows.

 

On Solaris and AIX we just use Subversion to check out the code. And
this is why I hope I would find a solution to my problem using
Subversion, instead of, as someone suggested, using a third-party editor
in Windows.

 

Visual Studio IS used to edit all files, as this is the main developing
platform. But when the code is checked out on Solaris to be built,
that's when we have the problem, because, as you said, Windows uses CRLF
and Solaris doesn't like that.

 

Thanks anyway

Giulio

 

________________________________

From: Barry Scott [mailto:barry@barrys-emacs.org] 
Sent: 02 November 2006 20:57
To: Giulio Troccoli
Cc: users@subversion.tigris.org
Subject: Re: svn:eol-style issue

 

 

On Oct 30, 2006, at 14:06, Giulio Troccoli wrote:

	Hi everybody,

	 

	I have an issue with the EOL and consequently with the
svn:eol-style property. I have found another post about it but it didn't
say how to solve the issue, and also it was a bit old so maybe now we do
have a solution.

	 

	The problem is across-platform problem. We have Subversion 1.3
installed on a Linux box, but the product is maintained on AIX, Solaris
and Windows. All developers use Visual Studio to do their job and
TortoiseSVN to commit the changes.

TSVN does not work on AIX or Solaris. How do you checkout the files on
those systems?

If you use TSVN to checkout onto a network file system that you share
with AIX then the line endings will be native to windows e.g. CRLF.

	 

	On AIX and Windows everything is fine, but on Solaris sometimes
the build failed because the compiler does not like the EOL of some
files. These happens (and strangely not always) when the files have been
edited using Visual Studio.

VS is a Windows tool and it only uses CRLF EOL. Don't use it to edit
unix files and things will work better.

Try using an editor that understands line endings. SciTE or Barry's
Emacs work with any EOL.

 

Barry