Re: Source package name with python- or without?
Scott Kitterman: On June 9, 2015 9:08:06 AM EDT, Thomas Goirand z...@debian.org wrote: On 06/08/2015 08:13 AM, Piotr Ożarowski wrote: [Tim Landscheidt, 2015-06-08] Should source package names (Source: in debian/control) be prefixed with python-? no. I use python- prefix for source package name only if the name is not unique enough. I have the opposite view, and I very much prefer to prefix with python- all of the source packages I upload, when that's a python module (I don't do that for applications). One very good reason for this is sorting the files when you do ls, or in your QA page, on gitweb/cgit, etc. Also, not polluting the general namespace is a good idea. If the upstream name isn't python-*, then the namespace is already polluted. Personally, I think upstream name for the source package is best unless it's really generic. Scott K I see this two ways: * if the source package only produces a single python- and python3- package, then I make the source package name with python- so that there are fewer names to keep track off, and it is easy to find the source package * if the source package produces more than one python- package and/or more than one python3- package, then I use the source name. .hc -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/557aec5d.70...@at.or.at
Re: Source package name with python- or without?
On 06/08/2015 08:13 AM, Piotr Ożarowski wrote: [Tim Landscheidt, 2015-06-08] Should source package names (Source: in debian/control) be prefixed with python-? no. I use python- prefix for source package name only if the name is not unique enough. I have the opposite view, and I very much prefer to prefix with python- all of the source packages I upload, when that's a python module (I don't do that for applications). One very good reason for this is sorting the files when you do ls, or in your QA page, on gitweb/cgit, etc. Also, not polluting the general namespace is a good idea. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5576e536.5080...@debian.org
Re: Source package name with python- or without?
On June 9, 2015 9:08:06 AM EDT, Thomas Goirand z...@debian.org wrote: On 06/08/2015 08:13 AM, Piotr Ożarowski wrote: [Tim Landscheidt, 2015-06-08] Should source package names (Source: in debian/control) be prefixed with python-? no. I use python- prefix for source package name only if the name is not unique enough. I have the opposite view, and I very much prefer to prefix with python- all of the source packages I upload, when that's a python module (I don't do that for applications). One very good reason for this is sorting the files when you do ls, or in your QA page, on gitweb/cgit, etc. Also, not polluting the general namespace is a good idea. If the upstream name isn't python-*, then the namespace is already polluted. Personally, I think upstream name for the source package is best unless it's really generic. Scott K -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e2290bf5-e8e6-4fd8-b6df-1472805c6...@kitterman.com
Re: Source package name with python- or without?
[Tim Landscheidt, 2015-06-08] Should source package names (Source: in debian/control) be prefixed with python-? no. I use python- prefix for source package name only if the name is not unique enough. -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150608061301.go11...@sar0.p1otr.com
Re: Source package name with python- or without?
On Jun 08, 2015, at 08:13 AM, Piotr Ożarowski wrote: I use python- prefix for source package name only if the name is not unique enough. Same. -Barry pgpBpCZep6NyA.pgp Description: OpenPGP digital signature
Source package name with python- or without?
Hi, at Wikimedia Tools (https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools) in the past we deployed several Python modules as packages gen- erated by py2dsc. I'm in the process of packaging them properly for Debian and have (so far) filed two ITPs to that effect. I want to maintain them as a member of the DPMT and would like to join the team for that (my alioth user name is scfc). In the past few days I have tried to process every one of the various policies and FAQs, but one very basic question that has remained unanswered for me is if the source package name should start with python- or not. https://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names states that names of /binary/ packages must be prefixed with python- (or python3-). Of the 774 packages/*/trunk/debian/control in the repository, 329 Source: values start with python-, three with python3-, and 442 with neither, so there is no obvious pattern. Most reflect the name of their repository path, but there are even exceptions to that (in both directions). Should source package names (Source: in debian/control) be prefixed with python-? Tim -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87ioaylvqi@passepartout.tim-landscheidt.de
