cvs commit: CVSROOT modules ports/shells Makefile
ports/shells/bash3 Makefile distinfo pkg-deinstall pkg-descr
pkg-install pkg-plist ports/shells/bash3/files patch-ac patch-af
patch-bashline.c patch-builtins_shopt.def patch-config-bot.h ...
eikemeier at fillmore-labs.com
Wed Aug 11 04:20:36 PDT 2004
Maxim Sobolev wrote:
> Hmmm, why do we have those "bash", "bash2" and "bash3"? There may have
> been some historical reasons for bash/bash2 separation, but I wonder if
> they are still valid for the bash2 vs bash3 case.
I guess bash 3.0 (like most .0 releases) has still some bugs to be
ironed out, see for example:
Therefore it seems wise to keep bash2 to run scripts until bash3 is
OTOH people might want to use the new bash3 features:
So having bash2 and bash3 is justified. Do you think the directories
should have different names?
More information about the cvs-all