Closed AMDmi3 closed 3 years ago
Debian uses python- and python3- prefixes for their python ports, however that onny apply to binary packages, not source ones, which are mosty unprefixed
This is not completely correct. In fact, Debian is an inconsistent mess, for instance:
Package: flask
Binary: python3-flask, python-flask-doc
Package: python-bottle
Binary: python3-bottle, python-bottle-doc
so we cannot even detect python modules by comparing their binary names with source names.
Binary packages support is not relevant here either, as source packages will still have this problem.
So not going to fix this - most Debian python modules will remain unmerged. Some may be merged manually, for example when there's a vulnerability to highlight.
Debian uses
python-
andpython3-
prefixes for their python ports, however that onny apply to binary packages, not source ones, which are mosty unprefixed. We need to include binary packages for debian (something I've wanted for a long time anyway), and some machinery which matches source/binary packages and propagates properties from one to another and/or to metapackage.After proper delta updates are implemented, we can drop prefixes (e.g.
python:
) and process all packages together, being able to propagate properties and only then split them into different projects (differentiated not by a name prefix, but by a additional namespace field or alike). This would allow to classify unprefixed source package based on related binary ones. Example package isslixmpp
.