Hello!Why do you need this? Does setup.py not install them?
pybuild is magic. It knows where the build directory is, despite it seemingly calling setup.py with no command line arguments specifying
it!
But anyway, my actual question is this. How do I ensure that the data
files are also copied into the package?
Only the .py files are currently included in the build; what is theApart from fixing setup.py? execute_after_dh_auto_install I guess.
best way to include all of the data files after the build step and
before the test step, and then to ensure they are included in the
final package?
Only the .py files are currently included in the build; what is theApart from fixing setup.py? execute_after_dh_auto_install I guess.
best way to include all of the data files after the build step and
before the test step, and then to ensure they are included in the
final package?
On 2021-12-01 12 h 28, Andrey Rahmatullin wrote:
Only the .py files are currently included in the build; what is theApart from fixing setup.py? execute_after_dh_auto_install I guess.
best way to include all of the data files after the build step and
before the test step, and then to ensure they are included in the
final package?
Or you can use debian/foobar.install to install the missing files in the right location, and keep your d/rules file cleaner :)
ex. (man dh_install):
https://sources.debian.org/src/sublime-music/0.11.16-1/debian/sublime-music.install/
I don't understand why the files are not correctly installed by
setup.py; it has set include_package_data=True, which includes the
files (and file patterns) listed in MANIFEST.in, but it seems that
this is only used for the bdist and sdist targets of setup.py, but not
for the install target.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 384 |
Nodes: | 16 (2 / 14) |
Uptime: | 63:34:04 |
Calls: | 8,174 |
Calls today: | 6 |
Files: | 13,113 |
Messages: | 5,864,702 |