On 7/27/23 15:24, Simon McVittie wrote:
On Thu, 27 Jul 2023 at 13:49:33 +0200, Timo Röhling wrote:
recently there have been two independent changes in the Python and
CMake world which conspired to FTBFS a number of packages.
TL;DR: export DEB_PYTHON_INSTALL_LAYOUT=deb_system in d/rules
Is "deb_system" and not "deb" the canonical thing to use here? The GNOME
team has been using "DEB_PYTHON_INSTALL_LAYOUT = deb" to work around
the corresponding issue with Meson-built packages.
It's effectively the same:
# default to /usr for package builds, /usr/local otherwise
deb_build = os.environ.get('DEB_PYTHON_INSTALL_LAYOUT', 'posix_local')
if deb_build in ('deb', 'deb_system'):
prefix_scheme = 'deb_system'
else:
prefix_scheme = 'posix_local'
https://sources.debian.org/src/python3.11/3.11.4-1/Lib/sysconfig.py/?hl=322#L322
The deb_system is suggested for package builds:
* sysconfig: The 'posix_local' schema name is the default unless the
env var DEB_PYTHON_INSTALL_LAYOUT is set to 'deb' or 'deb_system'.
Use the latter for package buillds.
https://sources.debian.org/src/python3.11/3.11.4-1/debian/changelog/?hl=1056#L1056
The changelog entry is the only documentation I've found for
DEB_PYTHON_INSTALL_LAYOUT.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
