Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16958
| From | Carsten Schoenert <c.schoenert@t-online.de> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Need help with naming scheme in debian/control for python library |
| Date | 2025-07-01 10:50 +0200 |
| Message-ID | <L3EQF-er1G-1@gated-at.bofh.it> (permalink) |
| References | <L3EQF-er1G-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hello Aryan, Am 01.07.25 um 09:59 schrieb Aryan Karamtoth: ... > So my question is should I rename the source field to “python3- > packagename” too or will it cause any conflicts? the common sense is to prefix the source package with "python" without any version numbers. And the bin package for a library with "python3" to mark the Paython main version the package is usable with. Contrary bin packages which contain documentation only then get the prefix "python" again, but also a suffix "doc". e.g. Source: python-upstream_name ... Package: python3-upstream_name Description: Shiny neat Python library to do $things ... Package: python-upstream_name-doc Description: Shiny neat Python library to do $things (Documentation) ... https://qa.debian.org/developer.php?email=team%2Bpython%40tracker.debian.org There you have a full overview of existing packages maintained by the DPT. Have a look at existing packages. -- Regards Carsten
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar
Re: Need help with naming scheme in debian/control for python library Carsten Schoenert <c.schoenert@t-online.de> - 2025-07-01 10:50 +0200 Re: Need help with naming scheme in debian/control for python library Andrey Rakhmatullin <wrar@debian.org> - 2025-07-01 11:40 +0200 Re: Need help with naming scheme in debian/control for python library Simon McVittie <smcv@debian.org> - 2025-07-01 18:00 +0200
csiph-web