Path: csiph.com!aioe.org!news.servidellagleba.it!bofh.it!news.nic.it!robomod From: Steffen Moeller Newsgroups: linux.debian.maint.python Subject: Re: on the lack of a `python-` prefix for source packages Date: Tue, 20 Dec 2022 01:00:01 +0100 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Mon Dec 19 23:56:32 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.901 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, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Ui-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:l7sXCVb4cDhAsl5rHVVwCOzfpY6pbhdPT4kuGcKCvTn9IBr7Xk8 XeCpnoeYqfiLRhmn8iyHPRgpg5J3Kub1SBa8BbBA36TudKzuDp864/maZtKZT5hgNNz20S9 9z2HQ3rS51RBIjO8IIyYMV2j+4AaTxBxDjQNmszEaQAj9Zl1+Cg7FqikWhlDdxwBuTi+USd xlo5Zhw/VZ33cB9ZqCA+Q== Ui-Outboundreport: notjunk:1;M01:P0:BKX9x1fuXIY=;mxhQEnq1PXYCJlSZQFFm35b6U3x yuxNdF0xvBte8MvcKcP6rvI4KijUDgL/n//MBjXtRmqtvL2J6jCbUI/PDxEAFauxgs7jytZhT W7udIcd53GKJCjl48fYXeQJi9kUt3bqQwQF4rxUr5V1boocLXvfsRjwI7ctHyHq+WNZdkhj/a wNJxOZ/o/xPjKJIeqnQQhRdDWH9Zch53lFi1Ah/MHZWNa2hxosv54rCpNBEpiuRSBAbTkvC2N 9bIiRJFbA4sa6JkiB/omzJFRi/Hqi4pxoif0yOMMBM9tGjyPkX6viWBC/+c4871uLhA5NaNXN j4aFNyPoYMt/qnmdif6NqL+m1IHJY0GzAwd1NRCOUMV76RBprY8a5rKgZi0xRkVjR/kQXFp5G 6RVZeGLze4VuEAJrp4ReWeRTK71v08zLSCOi0uKPYgeCn++JJ8OjYG/JCmU6y/2uP8q4zmlUl 3LnPOLY2EF6IY/UTD4RY9eLCqD3voSSkiXAA1cL7owe5w8/vOxvyu6Ow+iBoGTjfesfXG4gKw Opfv9R1wCKDWBwdoFpCX//ZsvgBS2833jB7Iap273dLPmFWdvF5KHKdAwzbA0kV/IxjOyjIYz BhMUZbLhy+tb8gsud0EN30WB0G1mrMPmvnmE0/+lD4j6F8zf0jYQXKEuQk3k2C+rRU6wfTbcL oHi6McTqsr8+K60XrgnQV+yqUSwMvhZp3iagyneey/W9Bx7HuV4o4cLDbXc1WG1MJGwrORZ9i X1CC1hJeZhcuM/xIGhhU2Mjl84juZzAhwuOSLq66KCUjeEZ17YHzKFHfAj3hvVXJm3Vf+6+TG RKqzZgObW8nZMrq8QCLY0OmcVtTal1FSMDGZR8JTBpEDAzgFHFpDoDBRZThdU8+RzSexqMii0 Sy5ILsYI23jgwnMPL0TDDZvx6VhMuRaFY7WRV6p5U9/jLQxjyKDIS8eU/3MwdRk/MqBcEy5Vq 0DfUpg8BXGoSDCsKiMkvBAAMZ/w= X-Mailing-List: archive/latest/20624 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/c7f34020-5b79-e3e7-b073-b7b99af6c395@gmx.de Approved: robomod@news.nic.it Lines: 40 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 20 Dec 2022 00:56:11 +0100 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.python:14757 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