You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Christian Geisert <ch...@isu-gmbh.de> on 2007/01/26 00:37:19 UTC
svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Jacques Le Roux schrieb:
> So what happend to Christian ?
ant had no svn:eol-style property at all which meant my svn client
checked it out as committed by you (windows eol in this case).
If it had eol-style = native my client would have converted the line
endings acording to my platform (LF).
ant.bat already has svn:eol-style CRLF.
I think it's a good idea to set the eol-style for platform specific
files like shell scripts to the correct value.
Christian
Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Posted by Jacques Le Roux <ja...@les7arts.com>.
Yes this make sense. I propose to set eol-style=LF for Unix specific files. Though native would also do it, but to be consistent we
should in this case put native for Windows specific files. Another way is to set native for all files.
Jacques
----- Original Message -----
From: "Christian Geisert" <ch...@isu-gmbh.de>
To: <de...@ofbiz.apache.org>
Sent: Friday, January 26, 2007 9:13 AM
Subject: Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
> David E. Jones schrieb:
> >
> > On Jan 25, 2007, at 4:37 PM, Christian Geisert wrote:
> >
> >> Jacques Le Roux schrieb:
> >>
> >>> So what happend to Christian ?
> >>
> >> ant had no svn:eol-style property at all which meant my svn client
> >> checked it out as committed by you (windows eol in this case).
> >
> > SVN shouldn't do this. It should be checked out for the default of your
> > platform unless you've specified otherwise in your client, or an
> > eol-style was specified on the server.
>
> If there is *no* eol-style property then subversion shouldn't change the
> file at all. Only when eol-style is set as native the line endings will
> be changed to your platform (if this wouldn't be the case why should we
> set the eol-style property?)
>
> > Was this checked out on a Windows machine? If so, then a Windows EOL is
> > what would be expected.
>
> It was on linux.
>
> --
> Christian
Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Posted by Jacques Le Roux <ja...@les7arts.com>.
I finally introduced svn:eol-style=LF for root Unix specific files in svn config file.
BTW I propose to commit http://www.opensourcestrategies.com/downloads/bshcontainer.bsh in OFBiz root if OpenSource Strategy is OK ?
Jacques
----- Original Message -----
From: "Jacques Le Roux" <ja...@les7arts.com>
To: <de...@ofbiz.apache.org>
Sent: Friday, January 26, 2007 10:54 AM
Subject: Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
> Christian,
>
> >From http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.3.5 I see :
>
> The solution to this problem is the svn:eol-style property. When this property is set to a valid value, Subversion uses it to
> determine what special processing to perform on the file so that the file's line ending style isn't flip-flopping with every
commit
> that comes from a different operating system. The valid values are:
>
> native
> This causes the file to contain the EOL markers that are native to the operating system on which Subversion was run. In other
> words, if a user on a Windows machine checks out a working copy that contains a file with an svn:eol-style property set to native,
> that file will contain CRLF EOL markers. ***A Unix user checking out a working copy which contains the same file will see LF EOL
> markers in his copy of the file***.
>
> Note that Subversion will actually store the file in the repository using normalized LF EOL markers regardless of the operating
> system. This is basically transparent to the user, though.
>
> CRLF
> This causes the file to contain CRLF sequences for EOL markers, regardless of the operating system in use.
>
> LF
> This causes the file to contain LF characters for EOL markers, regardless of the operating system in use.
>
> CR
> This causes the file to contain CR characters for EOL markers, regardless of the operating system in use. This line ending style
> is not very common. It was used on older Macintosh platforms (on which Subversion doesn't even run).
>
>
> So it seems that native will do it in any case (who care of .bat on Unix or .sh on Windows ?). For instance
> http://www.apache.org/dev/svn-eol-style.txt is ok with this assertion but
> *.dsp = svn:eol-style=CRLF
> *.dsw = svn:eol-style=CRLF
> any idea why ?
>
> Jacques
>
> From: "Christian Geisert" <ch...@isu-gmbh.de>
>
> > David E. Jones schrieb:
> > >
> > > On Jan 26, 2007, at 1:13 AM, Christian Geisert wrote:
> >
> > [..]
> >
> > >> If there is *no* eol-style property then subversion shouldn't change the
> > >> file at all. Only when eol-style is set as native the line endings will
> > >> be changed to your platform (if this wouldn't be the case why should we
> > >> set the eol-style property?)
> > >
> > > If you don't have the default eol-style in your client set to "native",
> > > then I VERY highly recommend it...
> > >
> > > You might even try the default OFBiz settings:
> > >
> > > http://svn.apache.org/repos/asf/ofbiz/site/svn/config
> > >
> > > I know this is a bit hidden and only really referred to in the "OFBiz
> > > Committers Roles and Responsibilities", here:
> > >
> > > http://docs.ofbiz.org/x/mQ
> >
> > Auto-props settings only effect new files that get checked into the
> > repository. They have no effect on checkouts.
> >
> > --
> > Christian Geisert
Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Posted by Jacques Le Roux <ja...@les7arts.com>.
Christian,
>From http://svnbook.red-bean.com/en/1.1/ch07s02.html#svn-ch-7-sect-2.3.5 I see :
The solution to this problem is the svn:eol-style property. When this property is set to a valid value, Subversion uses it to
determine what special processing to perform on the file so that the file's line ending style isn't flip-flopping with every commit
that comes from a different operating system. The valid values are:
native
This causes the file to contain the EOL markers that are native to the operating system on which Subversion was run. In other
words, if a user on a Windows machine checks out a working copy that contains a file with an svn:eol-style property set to native,
that file will contain CRLF EOL markers. ***A Unix user checking out a working copy which contains the same file will see LF EOL
markers in his copy of the file***.
Note that Subversion will actually store the file in the repository using normalized LF EOL markers regardless of the operating
system. This is basically transparent to the user, though.
CRLF
This causes the file to contain CRLF sequences for EOL markers, regardless of the operating system in use.
LF
This causes the file to contain LF characters for EOL markers, regardless of the operating system in use.
CR
This causes the file to contain CR characters for EOL markers, regardless of the operating system in use. This line ending style
is not very common. It was used on older Macintosh platforms (on which Subversion doesn't even run).
So it seems that native will do it in any case (who care of .bat on Unix or .sh on Windows ?). For instance
http://www.apache.org/dev/svn-eol-style.txt is ok with this assertion but
*.dsp = svn:eol-style=CRLF
*.dsw = svn:eol-style=CRLF
any idea why ?
Jacques
From: "Christian Geisert" <ch...@isu-gmbh.de>
> David E. Jones schrieb:
> >
> > On Jan 26, 2007, at 1:13 AM, Christian Geisert wrote:
>
> [..]
>
> >> If there is *no* eol-style property then subversion shouldn't change the
> >> file at all. Only when eol-style is set as native the line endings will
> >> be changed to your platform (if this wouldn't be the case why should we
> >> set the eol-style property?)
> >
> > If you don't have the default eol-style in your client set to "native",
> > then I VERY highly recommend it...
> >
> > You might even try the default OFBiz settings:
> >
> > http://svn.apache.org/repos/asf/ofbiz/site/svn/config
> >
> > I know this is a bit hidden and only really referred to in the "OFBiz
> > Committers Roles and Responsibilities", here:
> >
> > http://docs.ofbiz.org/x/mQ
>
> Auto-props settings only effect new files that get checked into the
> repository. They have no effect on checkouts.
>
> --
> Christian Geisert
Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Posted by Christian Geisert <ch...@isu-gmbh.de>.
David E. Jones schrieb:
>
> On Jan 26, 2007, at 1:13 AM, Christian Geisert wrote:
[..]
>> If there is *no* eol-style property then subversion shouldn't change the
>> file at all. Only when eol-style is set as native the line endings will
>> be changed to your platform (if this wouldn't be the case why should we
>> set the eol-style property?)
>
> If you don't have the default eol-style in your client set to "native",
> then I VERY highly recommend it...
>
> You might even try the default OFBiz settings:
>
> http://svn.apache.org/repos/asf/ofbiz/site/svn/config
>
> I know this is a bit hidden and only really referred to in the "OFBiz
> Committers Roles and Responsibilities", here:
>
> http://docs.ofbiz.org/x/mQ
Auto-props settings only effect new files that get checked into the
repository. They have no effect on checkouts.
--
Christian Geisert
Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Posted by "David E. Jones" <jo...@hotwaxmedia.com>.
On Jan 26, 2007, at 1:13 AM, Christian Geisert wrote:
> David E. Jones schrieb:
>>
>> On Jan 25, 2007, at 4:37 PM, Christian Geisert wrote:
>>
>>> Jacques Le Roux schrieb:
>>>
>>>> So what happend to Christian ?
>>>
>>> ant had no svn:eol-style property at all which meant my svn client
>>> checked it out as committed by you (windows eol in this case).
>>
>> SVN shouldn't do this. It should be checked out for the default
>> of your
>> platform unless you've specified otherwise in your client, or an
>> eol-style was specified on the server.
>
> If there is *no* eol-style property then subversion shouldn't
> change the
> file at all. Only when eol-style is set as native the line endings
> will
> be changed to your platform (if this wouldn't be the case why
> should we
> set the eol-style property?)
If you don't have the default eol-style in your client set to
"native", then I VERY highly recommend it...
You might even try the default OFBiz settings:
http://svn.apache.org/repos/asf/ofbiz/site/svn/config
I know this is a bit hidden and only really referred to in the "OFBiz
Committers Roles and Responsibilities", here:
http://docs.ofbiz.org/x/mQ
-David
>> Was this checked out on a Windows machine? If so, then a Windows
>> EOL is
>> what would be expected.
>
> It was on linux.
>
> --
> Christian
Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Posted by Christian Geisert <ch...@isu-gmbh.de>.
David E. Jones schrieb:
>
> On Jan 25, 2007, at 4:37 PM, Christian Geisert wrote:
>
>> Jacques Le Roux schrieb:
>>
>>> So what happend to Christian ?
>>
>> ant had no svn:eol-style property at all which meant my svn client
>> checked it out as committed by you (windows eol in this case).
>
> SVN shouldn't do this. It should be checked out for the default of your
> platform unless you've specified otherwise in your client, or an
> eol-style was specified on the server.
If there is *no* eol-style property then subversion shouldn't change the
file at all. Only when eol-style is set as native the line endings will
be changed to your platform (if this wouldn't be the case why should we
set the eol-style property?)
> Was this checked out on a Windows machine? If so, then a Windows EOL is
> what would be expected.
It was on linux.
--
Christian
Re: svn:eol-style (was Re: svn commit: r499759 - /ofbiz/trunk/ant)
Posted by "David E. Jones" <jo...@hotwaxmedia.com>.
On Jan 25, 2007, at 4:37 PM, Christian Geisert wrote:
> Jacques Le Roux schrieb:
>> So what happend to Christian ?
>
> ant had no svn:eol-style property at all which meant my svn client
> checked it out as committed by you (windows eol in this case).
SVN shouldn't do this. It should be checked out for the default of
your platform unless you've specified otherwise in your client, or an
eol-style was specified on the server.
Was this checked out on a Windows machine? If so, then a Windows EOL
is what would be expected.
-David
> If it had eol-style = native my client would have converted the
> line endings acording to my platform (LF).
>
> ant.bat already has svn:eol-style CRLF.
>
> I think it's a good idea to set the eol-style for platform specific
> files like shell scripts to the correct value.
>
> Christian