Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: Jeremy Stanley Newsgroups: linux.debian.maint.python Subject: Re: How should upstream document/communicate none-Python dependencies? Date: Thu, 02 Feb 2023 15:40:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Feb 2 14:35:04 2023 Old-Return-Path: X-Amavis-Spam-Status: No, score=-12 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, LDO_WHITELIST=-5, PGPSIGNATURE=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate:hard: -4.6 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2bj7qwtwa6o2vkuc" Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) X-Sa-Exim-Connect-IP: 2001:4802:7801:102:be76:4eff:fe20:63e0 X-Sa-Exim-Rcpt-To: debian-python@lists.debian.org X-Sa-Exim-Mail-From: fungi@yuggoth.org X-Sa-Exim-Scanned: No (on azathoth.yuggoth.org); SAEximRunCond expanded to false X-Mailing-List: archive/latest/20765 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20230202143444.3ldnsqkogltq7uxf@yuggoth.org Approved: robomod@news.nic.it Lines: 67 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 2 Feb 2023 14:34:44 +0000 X-Original-Message-ID: <20230202143444.3ldnsqkogltq7uxf@yuggoth.org> X-Original-References: <20230202134650.d2e4qu3jneci5h2q@yuggoth.org> <810aff0727dde5bfccd4daa3406828a1@posteo.de> Xref: csiph.com linux.debian.maint.python:14879 --2bj7qwtwa6o2vkuc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. --=20 Jeremy Stanley --2bj7qwtwa6o2vkuc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEEl65Jb8At7J/DU7LnSPmWEUNJWCkFAmPbyf9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk3 QUU0OTZGQzAyREVDOUZDMzUzQjJFNzQ4Rjk5NjExNDM0OTU4MjkACgkQSPmWEUNJ WCl48A/9GgznEK41tSzHivmd4M/UyQM8SnLLAz2Zfz8Bo+BkYLN8kNjj0ZnXku9s ei+2xXEYguvcms6gpKcdUe3BFHkzXa1IXqfLehQMI7p1kM5uTylMbQwivjDsyCYF i9tyPuKJmNHRHLv1ACi/rpJUA4VtK4HPNP2kfnp03ZvPERORg79nEXGy81DroxFa 1LB6Wtgjor3v43S0IGTK0xtL20A/tb1mHlopCLfkBteuZZDt6jiaiizG+GlCDT6P ym2oOLPYwqAHL2wvk0NV6xrlDSa3bbgD8CX0ywIx64L4izrdVZrm/+jfDZeO7dXE MoBLfgoTccLUtk1Kh4Eq3WIV9ujhYfu6tcylyhRkVk+CbvMbjrKmayvsZtTWXPOL eA/AS0tzpxFEw6DQm7tQaL+OHfb7L9U2O398PkJgrCVqYbmnY0N7FejZDjRqJQp/ YmsazKbnbQOkd/tJo/xNzKvcV3o2luoYNMVBW5hYEUWykUjeACf5uK+M24l5wifG G6AE5qT3uW5tLf0vmnPU7JXP+3tkMrrVvlr9vUIxledTb8YcHDDI8EAqjKN98cwv 1AtArJAqMuoA83P5XPDS38XBk1xc2klHpWtRiAY4H45tuHoYEq/SamK6oeaGyuXI hAYtoMDi6BKbcwoeYk3ocwKlb+mhu+N8MNOdUCU9pq/C+bsSCDQ= =lHZ4 -----END PGP SIGNATURE----- --2bj7qwtwa6o2vkuc--