Hi, I think it would help to distinguish between upstream github source repos, debian source packages and debian binary packages to better understand all the past and current naming.
Previously :
Github source | Debian source packages | Debian binary packages
---------------------------------------------------------------------------
Qiskit/qiskit | src:qiskit-terra | qasm-simulator-cpp [any]
| | python3-qiskit [all]
| | qiskit-doc [all]
Now :
Github source | Debian source packages | Debian binary packages
---------------------------------------------------------------------------
Qiskit/qiskit-terra | src:qiskit-terra | python3-qiskit-terra pka
python3-qiskit [all]
---------------------------------------------------------------------------
Qiskit/qiskit-aer | src:qiskit-aer | qiskit-aer pka
qasm-simulator-cpp [any]
---------------------------------------------------------------------------
Qiskit/qiskit | src:qiskit-doc | qiskit-doc [all]
Am I correct restating things this way ?
Dependencies (runtime/build) on the Debian side are dealt by each
package not the pip setup so Qiskit/qiskit's role would only be to
provide documentation, thus the src:qiskit-doc Debian source package name.
The point is, if one starts reworking the packaging, we should not
undergo another package (upstream/source/binary) renaming too often.
The condition for packaging in Debian is also that the upstream software
should be in a stable state.
F.
pgpjY2xolHs1s.pgp
Description: PGP signature
