On Sat, Jun 10, 2023 at 09:21:19PM +0200, Sven Joachim wrote: > Unfortunately neither the Debian changelog of dash nor the commit > message for this change[2] give an explanation. Removing the debconf > handling certainly simplifies the package, and there are not too many > scripts around that start with "#!/bin/sh" and fail to work with dash - > these are the reasons I can think of.
I have serious doubts about that. I'm sure that *in Debian*, virtually all scripts have been fixed to use the correct syntax for their shebang. But outside of Debian? The world's a mess. There's no way to even know how many broken scripts are out there. An admin's choice to use /bin/sh -> bash on their system is usually done to work around broken third-party scripts. (This is what's so confusing about S M's part of the thread -- their motivation is entirely different.) At the bare minimum, this change needs to be documented in the official release notes and the dash NEWS file, which is currently giving incorrect information to users. It would also be *nice* to have an explanation, and perhaps some risk analysis about what may happen if an admin decides to change the symlink despite the unsupported nature of that change. I suspect we'll only get the latter from users who are brave enough to try it, and dedicated enough to document their discoveries.
