----- Original Message -----
From: "Zbigniew Jędrzejewski-Szmek" zbyszek@in.waw.pl To: "Development discussions related to Fedora" devel@lists.fedoraproject.org Sent: Wednesday, January 20, 2016 11:54:30 PM Subject: Re: Python naming guidelines clarification
On Wed, Jan 20, 2016 at 09:44:50PM +0100, Jan Včelák wrote:
Hello.
I've got several Python packages on review. But I'm not sure if the naming policy applies to the spec file the same way as it applies on the resulting packages.
socketIO-client RHBZ #1300092 ripe-atlas-sagan RHBZ #1300217 ripe-atlas-cousteau RHBZ #1300219
Yes, the guidelines apply to the source rpm name too. Those srpms should be called python-*, because they contain python libries.
ripe-atlas-tools RHBZ #130022
This one contains an application (too), so the current srpm name is fine.
Looking at the ripe-atlas-tools documentation I couldn't find any mentions about using ripe-atlas-tools as a python library, therefore you don't have to split package into python2 and python3 subpackages and just build ripe-atlas-tools which will contain all the executables and its backend modules built with python3.
I don't see an use case for python2 subpackage, or am I missing something?
Zbyszek
devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
-- Robert Kuska {rkuska}