Dear Bas,
Il 12/08/26 07:10, Sebastiaan Couwenberg ha scritto:
On 8/11/26 10:48 PM, Antonio Valentino wrote:
Dear Bas,
[...]
This is an issue for the current implementation because all the
debian packages now have the same version.
Do you know if it is possible to control the version of the
individual packages generated form the same source tarball?
Binary packages don't have to use the same version of the source
package, this can sometimes be used instead of an epoch.
How can I do it?
Using substvars in d/control, e.g:
Package: pystac-ext-eo
Version: ${pystac-ext-eo:Version}
and generating the pystac-ext-eo.substvars file in d/rules using
the .toml files.
https://www.debian.org/doc/debian-policy/ch-source.html#variable-
substitutions-debian-substvars
thanks
[...]
Unless you have a different advice, I think that the cleanest
solution would be to have 25 independent packages and to get the
source tarballs from PyPI.
My gut feeling right now is that we don't want all of these separate
extension packages, but I don't have enough information to formulate
what I think would be the best solution.
For the time being I would like to keep the single source package.
Probably it is also a good idea to have only
python3-pystac-core
python3-pystac (which includes all the extensions and depends on
pystac-core)
May rename it to python3-pystac-extensions if it only contains those.
That could also be split into its own source package which bundles all
the extension like nodejs packages do (using the checksum version and
multiple upstream tarballs).
https://wiki.debian.org/Javascript/GroupSourcesTutorial
The upstream pystac is mostly a virtual package depending on all the
extensions. It only provides a single python module:
pystac/extensions/ext.py.
The debian version now provides the entire content of the
pystac/extensions sub-package.
I decided to keep the name such that packages currently depending on
pystac keep working.
python3-pystac-doc
python3-pytest-pystac would also be needed for autopkgtests
This one would be the only one with a mismatch between the debian
package version and the python package version.
pytest-pystac also doesn't have tags in the upstream repo, unlike core
and the extensions. Possibly because it hasn't been blessed as stable yet.
I managed to remove also the pytest-pystac package (it is only used at
build time and in autopkgtest)
The only new package now is python3-pystac-core.
Please feel free to review an upload.
kind regards
--
Antonio Valentino
_______________________________________________
Pkg-grass-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
