Name: Mksh
Homepage: https://www.mirbsd.org/mksh.htm
Why should you include it: Mksh is more lightweight than bash or zsh, yet more functional than ash/dash. It allow portable scripts, does sizing and terminal adjusting better IMO.
It is open source, yes.
A link for to the most recent tarball: http://www.mirbsd.org/MirOS/dist/mir/mksh/mksh-R56c.tgz
Edit: a new version came out.
Edit2: a new minor version came out.
Some commercial CAD software I use depends on many ksh (ksh93) scripts. In my test, those scripts work on mksh as well.
The original ksh93 has open-sourced in Oct 2017, and is being actively worked on (https://github.com/att/ast). However, they don't seem to have a release date in sight.
In this case, I think I will use mksh instead of ksh, at least for now.
@hashhsah it may be a bit obvious to state, but my method so far is to simply compile mksh and add it to the shell list.
Generating a eopkg build and posting it here can also be useful while it is not yet in the repo.
@bennydarshan I was sharing my experiences and use cases in support of including mksh into solus repo.
I've local eopkg built for both the github version of ksh93 and mksh.
However solus policy says that I shouldn't submit patches before the package is accepted. so I'm holding back my packages.
Anybody getting the tests to run properly in mksh using solbuild? Tests run perfect when building on my system, but as soon as I use solbuild, it complains about a missing tty (fd I think) and fails the check stage.