It is possible to select busybox's ash shell by using `eselect sh set busybox`, but busybox ash is not listed as an option, despite being part of @system.
Do you think that 'bb' (the statically linked version) should be an option as well?
(In reply to comment #1) > Do you think that 'bb' (the statically linked version) should be an option > as well? The statically linked version wastes memory in comparison to the dynamically linked version and provides no benefit over it.
Fixed in 0.4.
[ebuild R ] app-eselect/eselect-sh-0.4-r2::gentoo 0 KiB [ebuild R ] sys-apps/busybox-1.24.1::gentoo USE="ipv6 savedconfig static -debug -livecd -make-symlinks -math -mdev -pam (-selinux) -sep-usr -syslog (-systemd)" 0 KiB # eselect sh list Available POSIX shell implementations: [1] bash * Is this why the bug is CONFIRMED and not FIXED?
Ping. Adding busybox to "SYMLINK_TARGETS=( bash dash posh mksh )" shouldn't be that hard.
Now that I think of it, if busybox is selected, a warning about CONFIG_PREFER_APPLET/CONFIG_SH_STANDALONE possibly breaking scripts should be given.
I've looked through the history and I see that this addition was reverted because busybox shell silently replaces system tools with its own, and breaks stuff. Therefore, this is not going to be officially supported.
(In reply to Michał Górny from comment #7) > I've looked through the history and I see that this addition was reverted > because busybox shell silently replaces system tools with its own, and > breaks stuff. Therefore, this is not going to be officially supported. This is precisely what was pointed out in comment #6.