Re: How should upstream document/communicate none-Python dependencies?

2023-02-02 Thread Jeremy Stanley
On 2023-02-02 14:16:11 + (+), c.bu...@posteo.jp wrote: [...] > The upstream maintainers have to create a binddep.txt file. Yes, it would look something like this: https://opendev.org/openstack/nova/src/branch/master/bindep.txt And then projects relying on it document using the bindep too

Re: How should upstream document/communicate none-Python dependencies?

2023-02-02 Thread Joost van Baal-Ilić
Hi, Op Thu, Feb 02, 2023 at 01:10:03PM + schreef c.bu...@posteo.jp: > > 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

Re: How should upstream document/communicate none-Python dependencies?

2023-02-02 Thread c . buhtz
Thanks for your reply. Am 02.02.2023 14:46 schrieb Jeremy Stanley: with https://pypi.org/project/bindep which is effectively a manifest of distribution package names and a grammar for indicating Awesome. The upstream maintainers have to create a binddep.txt file. And the distro maintainers do

Re: How should upstream document/communicate none-Python dependencies?

2023-02-02 Thread Jeremy Stanley
In the OpenStack ecosystem we mostly solved this around 8 years ago with https://pypi.org/project/bindep which is effectively a manifest of distribution package names and a grammar for indicating differences in package naming or requirements between different distributions and versions thereof. It'

How should upstream document/communicate none-Python dependencies?

2023-02-02 Thread c . buhtz
Hello, 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 speci