| Summary: | Build issue: fusion-icon does not install python module in python_sitelib | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Francois Andriot <albator78> |
| Component: | non-core programs | Assignee: | Michele Calgaro <michele.calgaro> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | albator78, bugwatch, kb9vqf, michele.calgaro |
| Priority: | P5 | ||
| Version: | 3.5.13 [Trinity] | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Bug Depends on: | |||
| Bug Blocks: | 2014 | ||
| Attachments: | Fix installation directory for python module | ||
|
Description
Francois Andriot
2012-08-04 04:23:29 CDT
Created attachment 749 [details]
Fix installation directory for python module
The build sequence for this package should now be:
# Finds the python library directory
PYTHON_SITELIB="$(python2 -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())")"
# Builds the stuff
make
# Install files in correct locations
make install \
DESTDIR=/tmp/destdir \
PREFIX=/opt/trinity \
PYTHON_SITELIB=${PYTHON_SITELIB}
The current patch looks a bit hacky--the Python directory detection should be included in the Makefile rather than requiring an external command to be run first. Can we put PYTHON_SITELIB=$((python2 -c "from distutils.sysconfig import get_python_lib; print(get_python_lib())") at the top of the Makefile to set the variable automatically when make is run? Commit 7aa39b5 fixes the installation location for *non* Debian/Ubuntu distros, introducing auto-detection in the makefile. Francois, could you test on your system and let me know if it is ok now? Commit ed3904e (packaging) fixes the installation location for Debian/Ubuntu distros, which do not rely on the makefile to build the package. The bug should now be solved, but before closing it I will wait for Francois's feedback. Works OK for me. Thanks for the feedback and for the original patch. |