In this case, the interpreter dependency is written as
Requires: /usr/bin/env
rather than as a run-time probe
Requires: executable(python)
which will be satisfied if "python" is an executable
found on PATH, just like /usr/bin/env behavior.
(Note: executable(...) is added in rpm-4.4.3 or later).
Since run-time probes in rpm are controversial, it will likely be
a few more years before the functionality is reliably
deployed.
Your best bet in the interim is patching all the scripts to have
#!/usr/bin/python
Annoying, but patching will lead to more reliable packaging.
73 de Jeff
On 9/18/07,
Tarjei Knapstad <tarjei.knapstad@xxxxxxxxx> wrote:
Hi all,
I'm packaging some python scripts into an RPM. The first line of each
script has:
#!/usr/bin/env python
It seems like rpmbuild is adding this as an implicit requirement. My
problem is that if I build this on a box with python 2.3, the package
ends up requiring /usr/bin/python2.3. How can I get rid of this
implicitly added package requirement?
Regards,
--
Tarjei Knapstad
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
