[PATCH 2/2] Split bash compatible extensions into separate options.

Kang-Che Sung explorer09 at gmail.com
Wed Jan 11 05:18:50 UTC 2017


On Wed, Jan 11, 2017 at 3:17 AM, Kang-Che Sung <explorer09 at gmail.com> wrote:
> (Note: this is a large patch. Patch included as mail attachment)
>
> All of the bash compatibility options will now depend on
> CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an option that
> alone doesn't add any code.
>
> Splitting these options allows more flexibility in configuration, and
> makes it self-documenting about what bash-compatible features we have.
>
> Signed-off-by: Kang-Che Sung <explorer09 at gmail.com>
> ---
>  coreutils/test.c |   8 ++-
>  shell/ash.c      | 216 +++++++++++++++++++++++++++++++++++++------------------
>  shell/hush.c     | 133 ++++++++++++++++++++++------------
>  3 files changed, 239 insertions(+), 118 deletions(-)

Oops. I missed the ASH_BASH_COMPAT help text. It should be the same as
hush's one.

//config: help
//config:  Saying N to this will skip all options about bash-compatible
//config:  extensions. This option alone does not add any code.


More information about the busybox mailing list