On 10.10.2017 12:04, Richard Biener wrote:
On Mon, 9 Oct 2017, Dirk Müller wrote:
Hi, ... - env-script-interpreter: This is a new check that has a Badness of 9. The value is so low because it triggers tremendously often right now. Basically, for shell scripts installed with chmod +x in the typical binary directories like /usr/bin and the like, it is alerting when the script shebang starts with "#!.*env ". The intention here is to avoid the rpm-dependency logic add a file-depends on /usr/bin/env (which is useless) and have the *actual* interpreter added as dependency instead. So to silence the warning, something like
sed -i -e "1 s,#! */usr/bin/env python,#!/usr/bin/python2," %{buildroot}/%{_bindir}/*.py
is needed. This lets the rpm-dependency magic add a proper file-depends on /usr/bin/python2, pulling in python-base if it isn't installed already.
Huh, why not fix RPM instead?
In addition to what Neal said: using `#!/usr/bin/env` is a bug in almost all cases. It means that a distro-provided script runs on an unspecified interpreter randomly found in user's $PATH. The RPM behavior re dependencies is a minor bug; the buggy script is a bigger problem. To fix it, we would need a brp or some other mechanism to rewrite the actual installed scripts. regards m.
Richard.
-- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org