Opened 16 years ago
Closed 13 years ago
#11184 closed Bug (fixed)
scripts/rpm-install.sh does not respect options passed to setup.py
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | Uncategorized | Version: | 1.0 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Setuptools supports changing the target installation environment when building an RPM (setup.py bdist_rpm
) with the --python
or --fix-python
options. These have the effect of changing the path to the python executable to invoke in the generated .spec
file.
However, Django's setup.py
specifies a custom installation script in scripts/rpm-install.sh
, which always invokes python
directly:
... # This is what dist.py normally does. python setup.py install --root=${RPM_BUILD_ROOT} --record="INSTALLED_FILES" ...
As a result, it's impossible to generate a Django install to target non-default environments.
Attachments (1)
Change History (7)
comment:1 by , 16 years ago
milestone: | 1.1 |
---|
comment:2 by , 16 years ago
This can be worked around by manually specifying the correct path in scripts/rpm-install.sh
before running setup.py
.
comment:3 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|
by , 15 years ago
Attachment: | t11184-r11366.patch added |
---|
use ${python} instead of python in rpm-install.sh
comment:4 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → Bug |
comment:5 by , 13 years ago
Easy pickings: | unset |
---|---|
Triage Stage: | Accepted → Ready for checkin |
UI/UX: | unset |
Based on http://fedoraproject.org/wiki/Packaging:Python#Macros this looks OK.
Not 1.1 material at this point.