Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Joost van =?utf-8?Q?Baal-Ili=C4=87?= Newsgroups: linux.debian.maint.python Subject: Re: How should upstream document/communicate none-Python dependencies? Date: Thu, 02 Feb 2023 15:20:01 +0100 Message-ID: References: X-Original-To: c.buhtz@posteo.jp X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Feb 2 14:19:53 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.2 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_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Greylist: delayed 523 seconds by postgrey-1.36 at bendel; Thu, 02 Feb 2023 14:19:35 UTC Authentication-Results: eklund.uvt.nl; dmarc=pass (p=reject dis=none) header.from=uvt.nl Authentication-Results: eklund.uvt.nl; dkim=pass (2048-bit key; secure) header.d=uvt.nl header.i=@uvt.nl header.b="qSNWmlyq"; dkim-atps=neutral Authentication-Results: elekes.uvt.nl; none MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-URL: http://mdcc.cx/ X-Accept-Language: nl, en User-Agent: Mutt/1.10.1 (2018-07-13) X-Rspamd-Server: engset X-Rspamd-Queue-ID: 5481DB4 X-Rspamd-Action: no action Authentication-Results: eklund.uvt.nl; spf=pass smtp.mailfrom=joostvb+debian-python@uvt.nl X-Mailing-List: archive/latest/20764 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20230202141048.GD16276@banach.uvt.nl Approved: robomod@news.nic.it Lines: 32 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: Debian python X-Original-Date: Thu, 2 Feb 2023 15:10:48 +0100 X-Original-Message-ID: <20230202141048.GD16276@banach.uvt.nl> X-Original-References: Xref: csiph.com linux.debian.maint.python:14878 Hi, Op Thu, Feb 02, 2023 at 01:10:03PM +0000 schreef c.buhtz@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 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")? Afaik there is no such thing. One hard problem to tackle first would be to map the name of e.g. an RPM package to the equivalent one in the Debian/dpkg world. These are sometimes, but _not_ always, the same... Bye, Joost