From owner-freebsd-ports@FreeBSD.ORG Thu Mar 12 14:40:54 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C37BC106567B for ; Thu, 12 Mar 2009 14:40:54 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from QMTA04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id 6D9DD8FC2C for ; Thu, 12 Mar 2009 14:40:54 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from OMTA13.westchester.pa.mail.comcast.net ([76.96.62.52]) by QMTA04.westchester.pa.mail.comcast.net with comcast id SDa31b00317dt5G54EguSd; Thu, 12 Mar 2009 14:40:54 +0000 Received: from daland.home ([24.34.211.11]) by OMTA13.westchester.pa.mail.comcast.net with comcast id SEgu1b00Z0FJTGg3ZEguGs; Thu, 12 Mar 2009 14:40:54 +0000 Received: from algo by daland.home with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Lhm5d-000DIw-3A; Thu, 12 Mar 2009 10:40:53 -0400 From: Alex Goncharov To: gesbbb@yahoo.com In-reply-to: <20090312103015.2ee5dbef@scorpio> (message from Jerry on Thu, 12 Mar 2009 10:30:15 -0400) References: <20090311210322.GA17971@ozzmosis.com> <20090312073556.GA39778@ozzmosis.com> <20090312112958.4d0cac92.ehaupt@FreeBSD.org> <76B7C6A4-B380-4224-AF69-03ABB1CE5175@lassitu.de> <20090312103015.2ee5dbef@scorpio> Message-Id: Sender: Alex Goncharov Date: Thu, 12 Mar 2009 10:40:53 -0400 Cc: freebsd-ports@freebsd.org Subject: Re: shells/bash-4.0 port horribly broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Goncharov List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Mar 2009 14:40:55 -0000 ,--- You/Jerry (Thu, 12 Mar 2009 10:30:15 -0400) ----* | I am having the exact same problem. Several of my scripts are now | failing. I have modified a few with the older "`" tic method to make | them work; however, I feel that the easiest thing would be to simply | revert to Bash-3. | | Was this some sort of 'improvement' by the Bash developers, or is it | an un-squashed bug? Breaking the $(command) substitution would be catastrophic and Bash 4.0 documentation claims support for it: http://tiswww.case.edu/php/chet/bash/bashref.html Bash Reference Manual This text is a brief description of the features that are present in the Bash shell (version 4.0, 29 December 2008). This is Edition 4.0, last updated 29 December 2008, of The GNU Bash Reference Manual, for Bash, Version 4.0. 3.5.4 Command Substitution Command substitution allows the output of a command to replace the command itself. Command substitution occurs when a command is enclosed as follows: $(command) or `command` Bash performs the expansion by executing command and replacing the command substitution with the standard output of the command, with any trailing newlines deleted. Embedded newlines are not deleted, but they may be removed during word splitting. The command substitution $(cat file) can be replaced by the equivalent but faster $(< file). -- Alex -- alex-goncharov@comcast.net -- /* * Every time I lose weight, it finds me again! */