I'm part of upstream maintainer team of "backintime" (BIT).
A modern Python project (which BIT is currently not) would specify dependencies and other build related information's into a pyproject.toml file.
But some Python applications (e.g. BIT) do have non-Python dependencies to specific Debian packages e.g. "rsync".
As upstream I do document that into README or somewhere else in a human readable file.
But is there a machine readable way to specify things like this? Maybe there is a special pyproject.toml section I don't know about yet? Or something
like MANIFEST or requirements files I've heard of but never used.
How would you wish this as distro maintainers?
Side question: Do you, as distro maintainers, have automatic tools to translate dependencies from pyproject.toml (e.g. "pyfakefs") into the
related Debian package (e.g. "python3-pyfakefs")?
The upstream maintainers have to create a binddep.txt file.
And the distro maintainers do need to use binddep do parse that file and "translate" it into the package names of their distro.[...]
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 379 |
Nodes: | 16 (2 / 14) |
Uptime: | 67:44:24 |
Calls: | 8,084 |
Calls today: | 2 |
Files: | 13,068 |
Messages: | 5,849,522 |