[RFC PATCH 0/1] Allow applets to be implemented as scripts

[Ron Yorston]

I said in previous emails that I considered there were two uses for
embedded scripts:

- to allow developers to include application-specific scripts that
  weren't appropriate for a general-purpose BusyBox binary;

- to allow applets to be implemented as scripts.

My previous patches only handled the first case.

In the latter case I expected applets implemented as scripts to have
many of the same features as native C applets:

- they should appear in the lists generated by the busybox applet;

- they should have an installation directory configured so they
  could be installed by 'busybox --install';

- they should respond to 'busybox --help applet' and 'applet --help';

- it should be possible to enable and disable them through the usual
  process of configuration;

- they should have dependencies on any required applets or features.

None of the above was to be enforced in the first case.

I've now reworked the current embedded script functionality to include
support for applets.  The following patch also reinstates the idea that
the 'embed' directory isn't part of the BusyBox release and is available
for arbitrary use by developers.

Ron