On Mon, 13 Jan 2020 10:27:41 -0500
Eli Schwartz <[email protected]> wrote:

> 
> Couldn't you also COPY mim.sh? Why add 500 bytes to *everyone*'s
> busybox, in order to save 224kb in one person's docker container? Why
> reserve the namespace "mim" so that no one else can ever use it on
> alpine (you cannot exactly "apk del" a busybox builtin, and just
> installing bash or zsh seems to be rather missing the point).
> 
> Why must every single small script that some people consider useful, be
> hardcoded into the busybox binary?
> 

All very excellent points, I fully agree.

Busybox is made available in source. The "include scripts" feature is made 
available so everybody can include their own favourite scripts in their own 
builds. The way I see it, this particular feature is there for that very 
purpose, so everyone can extend busybox (easily) by include their own favourite 
commands written in shell scripts, as opposed to writing a C applet extension.

Everyone builds and configures busybox slightly differently according to their 
needs.
If one person likes the mim.sh script, sure, go ahead and build a busybox that 
includes it.
It doesn't mean that everyone else who doesn't need it, needs to have that too. 

I carry a bunch of patches for busybox I build for my distro too. Once upon a 
time I submitted it for inclusion, but it wasn't accepted, because it was 
considered "non-standard", even though some people acknowledged that it was 
useful. Fine by me. I understand that my patches is probably most useful only 
for me and not for others. I can carry it myself; and I have been carrying my 
patches for years.

I remember that one of the criteria that busybox accepts for inclusion is that 
the applet to be included must be in widespread use and have corresponding 
__FULL__ versions somewhere (core-utils, util-linux, or whatever other *-utils 
or *-tools). It is very rare when busybox adds a non-standard applet; and it is 
for good reason that it does it that way.

If this is accepted, then what's next?

cheers!

-- 
James B 
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to