Re: Installing platform-independent resources outside the Python package (was: Specifying ‘--install-data’ for each binary package)

2013-09-09 Thread Piotr Ożarowski
[Jakub Wilk, 2013-09-09] > * Ben Finney , 2013-09-09, 13:36: > >* Use ‘.links’ to make a symlink for each package to > >‘usr/share//foofile’ at > >‘usr/lib/python${PYTHON_VERSION}/dist-packages/${DISTRIBUTION_NAME}/foofile’. > > How can you do that without hardcoding Python version? should I add

Re: Installing platform-independent resources outside the Python package (was: Specifying ‘--install-data’ for each binary package)

2013-09-09 Thread Jakub Wilk
* Ben Finney , 2013-09-09, 13:36: * Use ‘.links’ to make a symlink for each package to ‘usr/share//foofile’ at ‘usr/lib/python${PYTHON_VERSION}/dist-packages/${DISTRIBUTION_NAME}/foofile’. How can you do that without hardcoding Python version? -- Jakub Wilk -- To UNSUBSCRIBE, email to debia

Installing platform-independent resources outside the Python package (was: Specifying ‘--install-data’ for each binary package)

2013-09-08 Thread Ben Finney
Ben Finney writes: > In that case, I currently have no good solution. I had hoped to use > some Python standard-library resource access function to find the > files wherever they are installed. I have hacked a work-around: * Patch the ‘MANIFEST.in’ and ‘setup.py’ to omit all mention of the re

Re: Specifying ‘--install-data’ for each binary package

2013-09-02 Thread Ben Finney
Éric Araujo writes: > Are you sure? package_data files are installed alongside the Python > modules; I think --data-files only controls the files declared as > data_files. In that case, I currently have no good solution. I had hoped to use some Python standard-library resource access function t

Re: Specifying ‘--install-data’ for each binary package

2013-09-02 Thread Éric Araujo
Hello, Le 02/09/2013 09:32, Ben Finney a écrit : > Those files are specifically declared in the ‘setup.py’ call via the > ‘package_data’ option. To tell Distutils where those files go, > http://docs.python.org/2/install/index.html#custom-installation> > says the correct command-line option I shoul

Re: Specifying ‘--install-data’ for each binary package

2013-09-02 Thread Piotr Ożarowski
[Piotr Ożarowski, 2013-09-02] > | #! /usr/bin/make -f > | export PYBUILD_NAME=coverage > | export PYBUILD_INSTALL_ARGS=--install-data=/usr/share/{package}/ > | %: > | dh $@ --with python2,python3 --buildsystem=pybuild > > the only problem is... you need to wait for next dh-python release. o

Re: Specifying ‘--install-data’ for each binary package

2013-09-02 Thread Piotr Ożarowski
[Ben Finney, 2013-09-02] > PYTHON2_PACKAGE_NAME = python-coverage > PYTHON3_PACKAGE_NAME = python3-coverage > PYTHON2 = $(shell pyversions -vr) > PYTHON3 = $(shell py3versions -vr) > […] > > .PHONY: install-python% > install-python%: PACKAGE_NAME=$(if $(findstr > ${PYTHON3},%),${PYTHON3_PACKAGE_N

Specifying ‘--install-data’ for each binary package

2013-09-02 Thread Ben Finney
Howdy all, Howd can I write ‘debian/rules’ to specify the right ‘--install-data=’ value to ‘setup.py’ for each binary package? I'm working on modifying an existing Python package (‘python-coverage’) to install its arch-independent files to ‘/usr/share/${PACKAGE_NAME}/’. Those files are specific