Alexey Ivanov wrote:
> Hi,
>
> Till now we are using CVS as part of our development environment,
> in situation, where part of our developers work on Windows, while
> the other, greater part of them work on FreeBSD. Both parts work
> in the same project and with the same code but with native development
> tools, some of which on Windows cannot work with Unix-style line endings
> (LF) and require CR-LF. Unix developers, of cause, don't like CR-LF,
> they want LF.
>
> So, Windows CVS client (Cygwin) smartly solves this collision for us, since
> it can translate Unix LF to Windows CR-LF during checkout or update
> process, and in the reverse direction during code commit.
All cvs operations default to native line endings unless you tell it to
handle the file as binary '-k'. Cygwin has its own oddness, but it
doesn't matter with cvs.
> Now I've tested in or work process SVN 1.6.1: The repository (svn+ssh://) was
> built on FreeBSD server, and clients were on Windows and FreeBSD.
> Windows client was CollabNet client command line or Cygwin's - results
> was the same (we cannot use GUI clients since the need in automatization).
>
> As I've read in the SVNbook (red-bean)
> http://svnbook.red-bean.com/en/1.5/svn.advanced.props.file-portability.html#svn.advanced.props.special.eol-style
> - I can tune Subversion so, that when our code is committed under Windows -
> CR-LF will be translated to LF, so Unix developers will be happy.
>
> I can select the commit mode: to keep CR-LF in the code forever, to keep LF
> forever or to use "native" line endings.
>
> It was very pity for me, that all this tuning works only for commit operation,
> not for checkout or update.
>
> In other words: if Unix developer commits some code - Windows developer
> cannot receive it with Windows line endings even if this file has svn:eol-style=native
> property.
>
> This behavior contradicts to the description of "native" svn:eol-style property in the SVNbook,
> but it was that I've seen in my testing.
>
> Is there any solution?
That doesn't sound right. If you set eol-style=native before committing
(or have it set by a cvs2svn conversion or auto-props), then you
should get native line endings on checkouts, updates, etc. Perhaps you
committed, then set the property? Even then, it should be adjusted on
the next commit. I think you are seeing a cygwin issue where it makes
the svn app think it is on unix.
--
Les Mikesell
lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2283799
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-16 21:50:07 CEST