Vladimir Marek wrote:
[...]
The bash test harness is the only reference we have for determining
whether or not a particular version of bash -- about to be released
as part of Solaris -- works, or doesn't work. Ignoring failures in
the bash POSIX compatibility tests simply because "Milan Jurik
doesn't like these changes" is not a viable option.
Well, no need to make it personal.
I do not like receiving, and reading, interrogation emails consisting
mainly of complaints, interdiction assertions, and in the end nothing
constructive.
I have to admit I do not know what
exactly causes your change to bash configuration. If customer wrote a
bash script using whatever was documented in bash man page (even if that
was not defensive way of writing scripts), can your change break his
script? If yes, it needs to be weighted the gain of being 100% harness
successful and have happy(-ier) customers. Would you mind describing
what is the impact of the change in question to real life scripts? It
seems that it might change behavior of 'echo' builtin?
There is a bash 4.2 FAQ here detailing the many changes in 4.2:
http://tiswww.case.edu/php/chet/bash/FAQ
Compatibility with bash 4.1 for the builtin echo can be enabled in 4.2
with:
shopt -s compat41
shopt -s xpg_echo
--Stefan
--
Stefan Teleman
Oracle USA Corporation
stefan.tele...@oracle.com
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
