Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #15111
| From | Stefano Rivera <stefanor@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python, linux.debian.bugs.dist |
| Subject | Re: Naming of python binary packages |
| Date | 2023-08-11 17:20 +0200 |
| Message-ID | <H1C5H-15Ep-1@gated-at.bofh.it> (permalink) |
| References | <H1BCF-14HI-3@gated-at.bofh.it> <H1BCF-14HI-3@gated-at.bofh.it> <H1BCF-14HI-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Hi debian-python (2023.08.11_14:49:00_+0000) > I don't think the solution here is for your packages to use > distribution-derived names while everyone else's use the policy-defined > names. Can we rather come to a consensus on what we should be using? I should say, of course, that we have a history of groups of packages that diverge from this policy. e.g. the Django app packages, and some sphinx things (I think). Sometimes it makes sense to not name things python3-foo, but rather something more descriptive to the sub-community that the package is a part of. But this example was a run of the mill Python module, as far as I can tell. Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Naming of python binary packages Stefano Rivera <stefanor@debian.org> - 2023-08-11 16:50 +0200 Re: Naming of python binary packages Stefano Rivera <stefanor@debian.org> - 2023-08-11 17:20 +0200 Re: Naming of python binary packages Scott Kitterman <debian@kitterman.com> - 2023-08-11 17:30 +0200 Re: Naming of python binary packages Simon McVittie <smcv@debian.org> - 2023-08-11 18:20 +0200
csiph-web