[PATCH 3/3] unzip: add support for a non-standard (busybox only) -J NUM option

[Denys Vlasenko]

On Tue, Nov 7, 2017 at 8:03 AM, Eugene Rudoy <gene.devel at gmail.com> wrote:
> Its behavior is the same as that of tar's --strip-components=NUM.
>
> Based on https://git.busybox.net/busybox/commit?id=6c563e370d0f2f3cf36f3b274e8fe1392ca7125f
>
> function                                             old     new   delta
> unzip_main                                          2964    3088    +124
> .rodata                                            17268   17295     +27
> packed_usage                                        1808    1833     +25
> ------------------------------------------------------------------------------
> (add/remove: 0/0 grow/shrink: 3/0 up/down: 176/0)             Total: 176 bytes
>
> Signed-off-by: Eugene Rudoy <gene.devel at gmail.com>
> ---
>  archival/unzip.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
>  1 file changed, 54 insertions(+), 2 deletions(-)
>
> diff --git a/archival/unzip.c b/archival/unzip.c
> index 50205eb6e..d5a601a24 100644
> --- a/archival/unzip.c
> +++ b/archival/unzip.c
> @@ -51,18 +51,29 @@
>  //config:      bool "Support compression method 95 (xz)"
>  //config:      default y
>  //config:      depends on FEATURE_UNZIP_CDF && DESKTOP
> +//config:
> +//config:config FEATURE_UNZIP_J_NUM
> +//config:      bool "Provide non-standard -J NUM option"
> +//config:      default n
> +//config:      depends on UNZIP
> +//config:      help
> +//config:      Add support for a non-standard (busybox only) -J NUM option.
> +//config:      Its behavior is the same as that of tar's --strip-components=NUM.

I'm wary of adding incompatible extensions.
Why do you need this?
What would you do if you have to run your scripts
on a system with Info-ZIP's unzip?