Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <42AA42D9.1090007@cwilson.fastmail.fm> Date: Fri, 10 Jun 2005 21:48:09 -0400 From: Charles Wilson User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Making /bin/sh == bash. Has the time come? References: <20050610150729 DOT GA13181 AT trixie DOT casa DOT cgf DOT cx> <20050610231343 DOT 6A12713C0A7 AT cgf DOT cx> <20050611003817 DOT GB1106 AT trixie DOT casa DOT cgf DOT cx> In-Reply-To: <20050611003817.GB1106@trixie.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > Wow. I never expected that bash would actually be faster. > > I would appreciate getting a few more benchmarks for other packages. > If this holds out then moving to bash is a no-brainer. FWIW, there has been a concerted effort in libtool-2.0 to replace fork/exec'ed subprocesses with builtins whenever available (e.g. fork/exec on ash, but if SHELL=bash/ksh/..., use some builtin construct). This is bound to help with respect to configury-type "benchmarks" as projects upgrade their libtools. Thus, things are only going to get better, in the ash-vs-bash race. With respect to alternatives, I was thinking about packaging that up for cygwin anyway, because the new family of automake packages could use it, instead of the hacked-together pseudo-alternative scheme it's using now. I haven't had a chance to look into it yet, tho. -- Chuck -- 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/