Bug 691331 - fix eol issues in lcm when iccwork branch merge into trunk
Summary: fix eol issues in lcm when iccwork branch merge into trunk
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Build Process (show other bugs)
Version: master
Hardware: PC Linux
: P4 normal
Assignee: Hin-Tak Leung
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-21 01:32 UTC by Hin-Tak Leung
Modified: 2010-07-28 03:35 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hin-Tak Leung 2010-05-21 01:32:50 UTC
Just a place-holder to make sure we don't forget this, and need to co-ordinate to make sure nobody has uncommitted work in their lcms directory during the change.

Quite a few of the source code (*.c and *.h) files in the lcms have the executable bits set which shouldn't be; and quite a few unix shell script have CRLF line endings. The proper way to fix the former is "svn propdel svn:executable ..." and the latter is "svn propset eol-style native ...". The latter won't allow you to set the property unless the eol already matches, so this usually involves removing CR's. (see r11288)

r11289 and r11290 can be combined as this:

    find . -type f -executable  -exec file {} \; | \
     grep 'script text executable'  | \
    cut -f 1 -d ':' |xargs -n 1 svn propset svn:eol-style native
Comment 1 Hin-Tak Leung 2010-07-28 03:35:21 UTC
There have been quite a few CRLF/eol-related commits (e.g. 11380, 11376, 11313, 11312, 11310, 11309, 11308, 11291, 11290, 11289) and it is believed this is no longer an issue. Any remaining eol/CRLF issue is likely to be addressed when they are noticed.