simplifying the networking/Config.in WRT "ip"

[Jason Schoon]

On 4/14/06, Robert P. J. Day <rpjday at mindspring.com> wrote:
>
>
>   depending on what the visuals should be, it's not hard to cut down
> the amount of "ip"-related stuff in networking/Config.in as follows.
> for each of the four ip-alternative commands, do:
>
> config CONFIG_IPADDR
>         bool "ipaddr"
>         default n
>
> config CONFIG_IPLINK
> ... etc, followed by ...
>
> config CONFIG_IP
>         bool "Add ip equivalent commands to the above."
>         default n
>         help
>           Add the ip command to support equivalent commands to
>           ipaddr, iplink, iproute and iptunnel.
>
> config CONFIG_FEATURE_IP_ADDRESS
>         bool
>         default y
>         depends on CONFIG_IP && CONFIG_IPADDR
>
> ... remaining three as well.
>
>   obviously, this requires you to explicitly select what you want from
> ipaddr, iplink, iproute and iptunnel, with one final selection as to
> whether you want the "ip" versions of those commands as well.
> (clearly, you can go the other way as well.)
>
>   do those semantics make sense?  it clears a whole pile of
> unnecessary clutter out of Config.in, but it still leaves "ifupdown"
> making a mess of things.


That seems backwards in my mind.  "ip" is the actual command, with a bunch
of sub features.  The other alias (ipaddr, iplink, etc). are simply
shorthand for those who find it difficult to type it with a space (as far as
I can tell at least, I never use the short versions).

Would it make sense to have a single item beneath enabling IP, that said
something like "enable ip shorthand versions" (or something worded much
better).  Then, we could just enable the short version of whichever ip
subcommands had been selected.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.busybox.net/pipermail/busybox/attachments/20060414/d3df07fd/attachment-0002.htm