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

How should upstream document/communicate none-Python dependencies?

Path	csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod
From	c.buhtz@posteo.jp
Newsgroups	linux.debian.maint.python
Subject	How should upstream document/communicate none-Python dependencies?
Date	Thu, 02 Feb 2023 14:20:01 +0100
Message-ID	<FUHFn-2Uf8-1@gated-at.bofh.it> (permalink)
X-Mailbox-Line	From debian-python-request@lists.debian.org Thu Feb 2 13:10:24 2023
Old-Return-Path	<c.buhtz@posteo.jp>
X-Amavis-Spam-Status	No, score=-9.501 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -5.5
MIME-Version	1.0
Content-Type	text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding	7bit
X-Mailing-List	<debian-python@lists.debian.org> archive/latest/20761
List-ID	<debian-python.lists.debian.org>
List-URL	<https://lists.debian.org/debian-python/>
List-Archive	https://lists.debian.org/msgid-search/df0fac5a583d790549da977bc46e219c@posteo.de
Approved	robomod@news.nic.it
Lines	26
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Thu, 02 Feb 2023 13:10:03 +0000
X-Original-Message-ID	<df0fac5a583d790549da977bc46e219c@posteo.de>
Xref	csiph.com linux.debian.maint.python:14875

Show key headers only | View raw

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 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")?

Kind
Christian Buhtz

Back to linux.debian.maint.python | Previous | Next — 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