Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14876
| Path | csiph.com!1.us.feeder.erje.net!3.us.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!weretis.net!feeder8.news.weretis.net!news.szaf.org!fu-berlin.de!bofh.it!news.nic.it!robomod |
|---|---|
| From | c.buhtz@posteo.jp |
| 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 | <FUIBr-2UPb-5@gated-at.bofh.it> (permalink) |
| References | <FUHFn-2Uf8-1@gated-at.bofh.it> <FUIBr-2UPb-7@gated-at.bofh.it> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Thu Feb 2 14:16:32 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:hard: -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/20763 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/810aff0727dde5bfccd4daa3406828a1@posteo.de |
| Approved | robomod@news.nic.it |
| Lines | 16 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Date | Thu, 02 Feb 2023 14:16:11 +0000 |
| X-Original-Message-ID | <810aff0727dde5bfccd4daa3406828a1@posteo.de> |
| X-Original-References | <df0fac5a583d790549da977bc46e219c@posteo.de> <20230202134650.d2e4qu3jneci5h2q@yuggoth.org> |
| Xref | csiph.com linux.debian.maint.python:14876 |
Show key headers only | View raw
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 need to use binddep do parse that file and "translate" it into the package names of their distro. Am I right so far? What does other debian python package maintainers think about such a tool? Would this ease your (burden) of work preparing a new package (release)?
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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