[gs-bugs] [Bug 691331] New: fix eol issues in lcm when iccwork branch merge into trunk

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Fri May 21 01:32:52 UTC 2010


http://bugs.ghostscript.com/show_bug.cgi?id=691331

           Summary: fix eol issues in lcm when iccwork branch merge into
                    trunk
           Product: Ghostscript
           Version: HEAD
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: Build Process
        AssignedTo: hintak at ghostscript.com
        ReportedBy: hintak at ghostscript.com
         QAContact: gs-bugs at ghostscript.com
                CC: michael.vrhel at artifex.com
   Estimated Hours: 0.0


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

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list