Alan Coopersmith wrote:
On 11/30/11 07:33, Stefan Teleman wrote:
I've said it before, and I'll say it again: I don't change anything in
bash. I
only make certain the bash test harness passes 100% for every bash
release we
deliver as part of Solaris. If you are unhappy with the way bash
changes from
one release to another, I've already suggested an avenue for
alleviating your
concerns: become Tech Lead at bash upstream. You will then have 100%
control
over the future direction of bash.
We are not required to integrate every upstream release of bash into our
packages in exactly the state the upstream provides. If they provide a
release in which something is too broken to use, we can skip it and wait
for one in which it's fixed, or fix it and submit the patches upstream
Sorry, but this is simply not true:
1. We are required to integrate Userland components with as little
changes as possible, and we are also required *not* to deviate from
upstream to the extent possible, and not to create our own custom
designed forks.
2. Nothing here is "too broken to use". That is an unwarranted
exaggeration. It's a change in the bash echo builtin. No-one is
required to use it, and it can be explicitly disabled.
Do you have a concrete example of exactly what is "too broken to use"
in bash 4.2?
In any case, changing the way echo commands work in bash scripts is an
interface change you'll have to describe in an ARC case for this
integration.
3. There is no ARC case describing the interfaces provided by bash, or
its builtins.
--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
