Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #14876
| From | c.buhtz@posteo.jp |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: How should upstream document/communicate none-Python dependencies? |
| Date | 2023-02-02 15:20 +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> |
| Organization | linux.* mail to news gateway |
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