On 11/18/20 8:02 PM, Ludwig Nussel wrote:
Jiri Slaby wrote:
On 17. 11. 20, 14:55, Jan Engelhardt wrote:
With that, I find it prospective to just keep emptying /sbin and in doing so, drop the #UsrMerge blocks from specfiles, without going to %usrmerged, but straight to "done".
As a start, what about a post build check like we have for uses of /usr/bin/env after shebang? This would eliminate a lot, esp. for /bin/bash IMO.
To nag at packagers to patch all script to use /usr/bin/bash? That would be over the top IMO. It isn't wrong to use /bin/sh in shell scripts. That's kind of ABI IMO. We can't change /lib/ld-linux.so.2 hardcoded in binaries either after all. That's why the effort needs to be called usr merge rather than usr move :-) After the merge using either location works as it's the same.
The current one for /usr/bin/env is just a warning, plenty of packagers choose to ignore it and we have plenty of cases where it still exists (especially in python libs), so providing it as a warning is probably useful info for packagers should they feel like changing it in a cleanup, at the same time the review team shouldn't block packages with this warning from entering the distro. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B