[patch] proposed change to busybox option parsing.

[Rob Landley]

On Monday 05 September 2005 12:03, Aurelien Jacobs wrote:
> > This is a separate issue.
>
> Not completely... because you can't do such a thing anymore :
>   textutils --install -s

Could you ever?

If the applet supported textutils then it would run textutils when you invoked 
it under the name textutils.  Control wouldn't get to busybox_main() unless 
you invoked it under the name "busybox" or the name of an applet it didn't 
have.

> You would have to replace it with something like :
>   ln -s /bin/textutils /tmp/busybox-textutils
>   /tmp/busybox-textutils --install -s
>   rm -f /tmp/busybox-textutils

*boggle*

What exactly are you trying to do?

> Some people may consider this a regression...

Let's look at the 1.01 release, which does not have the new command line 
parsing:

--------
landley at driftwood:~/busybox/busybox_1_00_stable/busybox$ ./busybox
BusyBox v1.01 (2005.09.05-10:08+0000) multi-call binary

Usage: busybox [function] [arguments]...
   or: [function] [arguments]...

        BusyBox is a multi-call binary that combines many common Unix
        utilities into a single executable.  Most people will create a
        link to busybox for each function they wish to use and BusyBox
        will act like whatever it was invoked as!

Currently defined functions:
        busybox, uniq

landley at driftwood:~/busybox/busybox_1_00_stable/busybox$ ln -s busybox uniq
landley at driftwood:~/busybox/busybox_1_00_stable/busybox$ ./uniq --install -s
./uniq: invalid option -- -
BusyBox v1.01 (2005.09.05-10:08+0000) multi-call binary

Usage: uniq [OPTION]... [INPUT [OUTPUT]]

landley at driftwood:~/busybox/busybox_1_00_stable/busybox$
--------

What _are_ you talking about?

> Aurel

Rob