É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
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
[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
[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
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
5 matches
Mail list logo