[RFC PATCH v2] Allow applets to be implemented as scripts

[Eli Schwartz]

On 11/7/18 2:42 AM, Ron Yorston wrote:
> Kang-Che Sung wrote:
>> Let no script applets individually configurable in menuconfig. Let users
>> resolve the dependencies of whatever they put in applets_sh.
> 
> My view is that if script applets are provided as part of BusyBox they
> should have all the features of native applets, including the usual
> configuration facilities.

Why has busybox *ever* provided documentation on "how to write simple
shell scripts and cp them to your system"?

Why ask for considerable trouble by attempting to install things which
are *always* inferior to existing tools on the target system, and which
don't even have the advantage of native applets?

The simple solution is to simply rm that directory. If vendors wish to
provide "quick hack" scripts to fulfill some *highly* specific, custom
need, then fine, let them embed some shell script into their busybox
binary. But I don't see why busybox should be in the business of
operating as a vendor and upstream provider of such scripts.

If you absolutely must provide these scripts, move them to docs/ --
including nologin -- which is more descriptive of their initial
intention. Leave a stub readme in the embed directory, since git does
not allow checking in an empty directory node.

...

It shouldn't affect me though, since as a desktop distributor of busybox
I will simply nope out of this entire patch series with alacrity.

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20181109/0bdf37d9/attachment.asc>