Hello Christian, Am 14.02.26 um 12:59 schrieb [email protected]:
Hello Folks, from my perspective as upstream maintainer I try to learn some internals.
Do you know and understand https://www.debian.org/doc/packaging-manuals/python-policy/
Imagine a modern Python application following PEP 517 & 621 (pyproject.toml and src-layout). Translations are handled via GNU gettext. Hatch(ling) is used as build system using "initialize" build hook to compile po into mo files and add them into the wheel. The application does access them via "importlib.resources". How does this interfere with Debian packaging? I don't want to create extra work for people like you. In a Debian package the mo files do not belong into the wheel but into /usr/share/locale. Is the Python build system relevant while Debian packing? Is pip used internally while you create the deb file? Or do you use your own way and the build system used by upstream does not matter?
The main rule in Debian is:There is no internet connection during build time. All needed dependencies *must* be available in de Debian archive.
I know you have a lot of tools to add extra ways and exceptions to overwrite upstream behavior. But I want to prevent that, spare your time and make it right from the very first beginning.
Is there already a similar package in the Debian archive? This can help to understand the process.
Do you have the project online so we can review it like a peer review?
Regards, Christian Buhtz
Regards -- Mechtilde Stehmann ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
OpenPGP_signature.asc
Description: OpenPGP digital signature
