Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #14879

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

Show key headers only | View raw

[Multipart message — attachments visible in raw view] - view raw

On 2023-02-02 14:16:11 +0000 (+0000), c.buhtz@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 tool like
this:

https://docs.openstack.org/nova/latest/contributor/development-environment.html#linux-systems

Another goal of that tool is for it to use a file format which is
reasonably human-readable, so that someone can work out dependencies
fairly quickly from it even if they can't or don't want to install
another tool to parse it.

> And the distro maintainers do need to use binddep do parse that file and
> "translate" it into the package names of their distro.
[...]

Yes, I don't know whether the OpenStack packaging team in Debian
relies on it at all, but the intent is for it to be usable by
prospective package maintainers for projects, at least as a means of
double-checking against their declared dependencies. Its grammar
allows projects to distinguish between arbitrary kinds of
dependencies through the use of free-form "profile" names and many
projects have settled on some common ones (particularly "test") to
separate hard dependencies from optional or testing-related
dependencies, but these concepts vary widely enough between
different distros that I wouldn't expect a package maintainer to
take the filtered bindep results directly without some manual
vetting.
-- 
Jeremy Stanley

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

How should upstream document/communicate none-Python  dependencies? c.buhtz@posteo.jp - 2023-02-02 14:20 +0100
  Re: How should upstream document/communicate none-Python  dependencies? c.buhtz@posteo.jp - 2023-02-02 15:20 +0100
    Re: How should upstream document/communicate none-Python  dependencies? Jeremy Stanley <fungi@yuggoth.org> - 2023-02-02 15:40 +0100
  Re: How should upstream document/communicate none-Python  dependencies? Jeremy Stanley <fungi@yuggoth.org> - 2023-02-02 15:20 +0100
  Re: How should upstream document/communicate none-Python  dependencies? Joost van Baal-Ilić <joostvb+debian-python@uvt.nl> - 2023-02-02 15:20 +0100

csiph-web