Hi Michal, Am Fr., 11. Feb. 2022 um 12:08 Uhr schrieb Michal Suchánek <msuchanek@suse.de>:
And that's exactly the problem. There are people already using busybox as a limited shell, and now you are adding dash to the mix.
I'm not forcing anyone to use the work that I'm doing. I understand your concern, and your concern is valid, that more variations in places where "it does not matter" just adds overhead and wins nothing. As my initial email indicated it is an experiment, and I submitted fixes for the fallout of that experiment and will continue to do so. I'm not forcing anyone to accept it though. In addition to that, what I learned while doing this *experiment* is that this problem is far simpler than I initially thought. The bulk of shell scripts that we run in package scriptlets are absolutely trivial and do not use nontrivial globbing or other features that could expose the commonly expected working subset of any posix like shell. There were issues like incorrect escaping or comments or plain syntax errors that bash happened to ignore or happened to just parse correctly. as these are undocumented quirks, it is possible that the next bash update causes them to fail mysteriously. Fixing this cruft is the absolutely right thing to do. Your webbrowser example is a good reason as well: rather than the webpage being "optimized to be viewed in IE", we want our webpages to be "optimized to run in any browser". I know anyones feedback if we happen to have some mandatory tool to use somewhere that doesn't work with firefox. Interoperability, open standards and open source belong together. Greetings, Dirk