[Distutils] Python interpreter path and bdist_rpm

Harry Henry Gebel hgebel@inet.net
Fri Sep 1 13:51:07 2000

On Fri, Sep 01, 2000 at 11:33:02AM -0400, Andrew Kuchling wrote:
> Question: should the RPM build script hard-core the full path of the
> interpreter binary, or does it cause problems?  If specifying the full
> path is OK, here's a patch.  (Harry, or someone else who knows RPM,
> should approve of this patch before considering checking it in.)

The problem with hard coding the path into the spec file is that it
prevents the source RPM from being built on a computer that does not have
python located in that place. I think a better solution would be something

env PATH=/usr/bin/:$PATH python setup.py bdist_rpm

Of course this only works if /usr/bin/python -> /usr/bin/python1.5 , if
/usr/bin/python -> /www/python/bin/python it won't work. If that is the
case, then maybe hard coding the path should be implemented as an option,
to be invoked with the understanding that it could hamper source RPM
portability. In practice I think most RPM-based distributions put python in
/usr/bin (I use RedHat, Mandrake, and SuSE on a fairly regular basis and
they all put it there), so it might only be breaking portability on a
theoretical basis (at least until python > 1.5 becomes common in

Harry Henry Gebel, Senior Developer, Landon House SBS        ICQ# 76308382
West Dover Hundred, Delaware