[Slackbuilds-users] Reverting system/busybox to Default Build Configurations

[B. Watson]

On Sun, 15 Sep 2024, Jeremy Hansen wrote:

> Personally, unless you know why the previous maintainer chose static, if might be worth making the default shared, and, if you desire (since you're the maintainer), you can make an
> option to make a static version.

I'm not the previous maintainer but I'm pretty familiar with
busybox... Most likely the use-case for static linking is, you can use
your statically-linked busybox tools to fix broken dynamic linking
(failed upgrade of glibc-solibs, or an accidental "rm -f" of a core
shared library).

If someone already has busybox installed, statically linked, and it
gets upgraded to a dynamically linked busybox... and then later on
needs it to fix .so breakage... that user will think "oh, good thing
I have a static busybox to fix this with", and then will be surprised
and mightily irritated that busybox is suddenly broken, too.

My vote would be, leave it static, and maybe add an option to make it
dynamic. Templates aren't there to be blindly adhered to 100% of the
time, they exist to give you a starting point.