X-Spam-Check-By: sourceware.org
Message-ID: <451AD796.2000805@cygwin.com>
Date: Wed, 27 Sep 2006 15:57:10 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.5) Gecko/20060727 Fedora/1.5.0.5-1.fc4.remi Thunderbird/1.5.0.5 Mnenhy/0.7.4.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Bash 3.1.17(8) CR/LF problem
References: <860934040609271241ib9c7486q60b651ac9b3d6c36 AT mail DOT gmail DOT com>
In-Reply-To: <860934040609271241ib9c7486q60b651ac9b3d6c36@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Malcolm Nixon wrote:
> I recently updated to Bash 3.1.17(8) and found my local build system
> failing due to the removal of CR/LF support:
> "A script on a binary mount that uses \r\n line endings will probably
> encounter syntax errors or odd variable assignments, because the \r is
> treated literally.  If this happens to you, use d2u to fix the line
> endings, or change your script to live in a text mount point.  A
> script  that resides on a text mount can have either line ending (even
> inconsistently mixed), but be aware that text mount points are
> slower,  due to \r\n filtering."
> 
> Unfortunately simply running "d2u" isn't a solution because:
>    * Some revision control systems make the files read-only.
>    * Some detect the change to <LF> as changes require manual merging.
>    * Some translate files to a "Local" format (CR/LF on Windows).
> 
> I think the bigger issue here is that this arbitrary change will break
> a "significant" number of existing scripts. I contract for a few
> companies that use Cygwin/Bakefile to achieve support for multiple
> compilers/tool-chains, and for hourly auto-build servers. This change
> will break all of them - some of which have been functional for over 4
> years.
> 
> In my opinion a better solution would have been to err on the side of
> compatibility and only use the new fast readline code if manually
> enabled.
> 
> Discussions around the local office this morning have resulted in the
> project manager being forced to consider branching a Cygwin mirror,
> rolling back Bash to 3.1.17(6) and mandating all developers use the
> intranet mirror and not grab any further web updates.


You forgot to make the argument of why using text mounts for the source 
directories isn't a reasonable solution?


-- 
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
216 Dalton Rd.                          (508) 893-9889 - FAX
Holliston, MA 01746

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/