On Jul 5, 2009, at 09:08, B. Smith-Mannschott wrote:
> On Sun, Jul 5, 2009 at 05:42, Cyrus Summers wrote:
>
>> I recently encountered an issue with svn:eol-style set to native.
>> While checking out / updating, svn changes all the files with
>> property
>> svn:eol-style=native the line endings to CRLF since I'm using
>> Windows,
>> the problem is that I also use Cygwin tools to build projects, and
>> the
>> shell script interpreter sh only recognize LF as the line ending
>> as in
>> *nix systems, the extra CRs are treated as error. So my current
>> solution is to change all the files the line endings back to its
>> original using dos2unix...
>
> Don't use svn:eol-style=native for *nix shell scripts, use
> svn:eol-style=LF instead. That way they'll always have LF line
> endings, regardless of which platform/client is in use when they are
> checked out. I would hope that anyone editing *nix shell scripts on
> windows is competent enough to use an editor other than notepad.
I think his complaint is more that svn:eol-style is being set to
native for files in projects over which he has no control but would
still like to use, and therefore is wanting a way to deal with such
projects on the client side. To which I say: check the working copy
out in the environment where you want to use it. If you want to use
it in Cygwin, check it out using the svn command line client in
Cygwin, which will get the files with LF line endings. If you want to
use the files in Windows proper, check them out using a Windows
Subversion client and the line endings will be CRLF. Don't share
working copies between environments, to avoid issues with EOL style
and also symlinks.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2368185
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-07-06 00:44:42 CEST