X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Matthew Woehlke Subject: Re: Bash 3.1.9 and 3.2.4: igncr setting not effective for 'source'd files Date: Fri, 03 Nov 2006 09:01:51 -0600 Lines: 21 Message-ID: References: <2fc802c00610311212i7bcc6b06sca14c0fda6ac6346 AT mail DOT gmail DOT com> <45489E5A DOT 9030408 AT byu DOT net> <454AA1EF DOT 8080401 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.0 In-Reply-To: <454AA1EF.8080401@byu.net> X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Eric Blake wrote: > According to Matthew Woehlke on 11/2/2006 2:23 PM: >> Eric Blake wrote: >>> And while I'm at it, maybe I will figure out how to name my release >>> bash-3.1.3-5, so that the bash patchlevel is included in the cygwin >>> release number. >> I thought that was just a matter of what appears in setup.ini? (But >> maybe I am wrong...) > > setup.ini uses whatever name I give to the cygwin release tarball, but the > g-b-s (generic-build-script), which I still use to generate bash releases, > prefers reusing the upstream tarball name when possible. Bash is shipped > by the tarball name bash-3.2.tar..., not bash-3.2..tar.... So > it is just a matter of me tweaking g-b-s to include the patchlevel in the > cygwin release. Ah, then I misunderstood where the problem is. Anyway, good luck! -- Matthew "I don't question your existence -- God" (seen on a church billboard) -- 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/