shells/bash-4.0 port horribly broken

[Andrew W. Nosenko]

On Thu, Mar 12, 2009 at 1:48 PM, Stefan Bethke <stb at lassitu.de> wrote:
> Am 12.03.2009 um 11:29 schrieb Emanuel Haupt:
>
>>>> $ sudo make
>>>> ===>  Vulnerability check disabled, database not found
>>>> => bash-4.tar.gz is not in /usr/ports/shells/bash/distinfo.
>>>> => Either /usr/ports/shells/bash/distinfo is out of date, or
>>>> => bash-4.tar.gz is spelled incorrectly.
>>>> *** Error code 1
>>>>
>>>> Stop in /usr/ports/shells/bash.
>>>
>>> Update: After a recent ports tree update bash now builds correctly
>>> here.
>>
>> The update still remains broken:
>>
>> [fooman at portjail ~]$ pkg_info
>> bash-static-4.0.10_1 The GNU Project's Bourne Again SHell
>>
>> [root at portjail ~]$ set -x
>> [root at portjail ~]$ echo $(uname)
>> -bash: command substitution: line 25: syntax error near unexpected token
>> `)'
>> -bash: command substitution: line 25: `uname)'
>
> I also find this rather annoying.  I believe that a rather large percentage
> of people use bash as their default shell, so moving from 3.2 to 4.0 should
> have been preceded by a headsup or an entry in UPDATING.

Hmm...  But record in UPDATING won't cure the bug itself.  Or error in
the parsing

    $ echo $(ls)

construct is not a bug?  If it is not a bug but intended behavior,
then could someone point me to the appropriate part of documentation?

-- 
Andrew W. Nosenko <andrew.w.nosenko at gmail.com>