Date: Sat, 14 Mar 2009 08:42:28 -0400 From: Howard Goldstein <hg@queue.to> To: obrien@freebsd.org Cc: freebsd-ports@freebsd.org Subject: Re: Problem with Bash-4 and $(command) syntax Message-ID: <49BBA634.7040306@queue.to> In-Reply-To: <20090313155833.GB53926@dragon.NUXI.org> References: <721111.30542.qm@web39104.mail.mud.yahoo.com> <887176.71382.qm@web32105.mail.mud.yahoo.com> <20090313155833.GB53926@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
David O'Brien wrote: > I have to weigh all the screams of 'I want the newest Bash 4.0 *NOW*' > with testing. I didn't see the issue of $() as my .bashrc and scripts > are too old and just use ``. > I agree with you and appreciate your efforts. Maintaining a port like this one with so many moving parts is a non-trivial effort. Do though, please, consider a line in UPDATING, perhaps including the appropriate portupgrade / portmaster incantations for the folks in production environments who really need to get /usr/local/bin/bash back to 3.x (portmaster -o shells/bash3 bash4-#-x-y did it for me)(replacing the #-x-y with whatever's in shells/bash now) Optimally David do you think this should be treated like for ex python and install major version softlinks (bash3->bash or bash4->bash) to aid maintainers of bashN dependent ports? I think there may be a bunch :( logcheck is another one that doesn't like 4... Thank you again for your work here.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49BBA634.7040306>