Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #14757

Re: on the lack of a `python-` prefix for source packages

From Steffen Moeller <steffen_moeller@gmx.de>
Newsgroups linux.debian.maint.python
Subject Re: on the lack of a `python-` prefix for source packages
Date 2022-12-20 01:00 +0100
Message-ID <FEyd3-bP13-1@gated-at.bofh.it> (permalink)
References <FBFNL-a30x-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Am 12.12.2022 um 02:24 schrieb Sandro Tosi:
> Proposal: the DPT will start adding a `python-` prefix to NEW source
> packages names, unless the upstream project already contains it
>
> AFAICT all other major languages ecosystems packaging teams use a
> (semi?)mandatory tag to identify their source packages (results below
> from a very quick look at Sources, top results only):
>
> prefix: golang, rust, r, node, ruby, haskell, php, ocaml, python (on a
> voluntary basis), and others
> prefix+suffix: perl
>
> At the beginning, I remember being in favor of the current status quo
> in DPT, where each maintainer can choose to add `python-` if they feel
> like it, or just use the upstream name.
>
> Thru the years, i've grown more uncomfortable with this situation and
> i think the fact we dont mandate a `python` prefix in the team source
> packages names (and thus guiding the rest of the python packagers
> within Debian towards a common style) is detrimental to Debian as a
> whole, and we should change it.
>
> My proposal as stated at the top is to start from now on to prepend
> `python` to all NEW source packages in DPT, with the option to rename
-> `python-`
> existing packages at a later date.
>
> What are other team members' opinions on this?

I agree.

The only exception should be a package with an executable that just
happens to be implemented in Python. That is likely self-evident, but
when packaging such a new package then one is likely also packaging a
handful of its dependencies. Then all the dependencies likely got that
python- prefix and then one may be tempted to also give it to the
package featuring the executable.

Best,
Steffen

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar | Unroll thread


Thread

on the lack of a `python-` prefix for source packages Sandro Tosi <morph@debian.org> - 2022-12-12 02:30 +0100
  Re: on the lack of a `python-` prefix for source packages Scott Kitterman <debian@kitterman.com> - 2022-12-12 03:00 +0100
    Re: on the lack of a `python-` prefix for source packages Louis-Philippe Véronneau <pollo@debian.org> - 2022-12-12 03:20 +0100
      Re: on the lack of a `python-` prefix for source packages Sandro Tosi <morph@debian.org> - 2022-12-12 03:50 +0100
        Re: on the lack of a `python-` prefix for source packages Scott Kitterman <debian@kitterman.com> - 2022-12-12 05:40 +0100
          Re: on the lack of a `python-` prefix for source packages Joseph Nahmias <jello@debian.org> - 2022-12-20 15:50 +0100
  Re: on the lack of a `python-` prefix for source packages Steffen Moeller <steffen_moeller@gmx.de> - 2022-12-20 01:00 +0100

csiph-web