https://bugzilla.redhat.com/show_bug.cgi?id=1576792
--- Comment #9 from Robert-André Mauchin <zebob.m(a)gmail.com> ---
(In reply to Peter Robinson from comment #8)
> You misunderstood me maybe, my advice is to change the Source0
to have an
> archive name with both name and version instead of only the version:
>
> Source0:
>
https://github.com/mozilla-iot/webthing-python/archive/v%{version}/%{name}-
> %{version}.tar.gz
Personally I don't overly care about this, I have updated it locally, but
AFAICT there's no packaging policy either way about this so it should not
block the review.
> The policy is still to make a subpackage even if you only make a python3
> version. I asked about this a few moths back on IRC.
Can you please provide the reference to this in the guidelines.
If I asked on IRC, it's because I didn't find it in the guidelines:
2018-02-26 18:25:47 eclipseo If a python package only supports Python 3,
should the package be named python-module with a python3-module provide, or
should it be named python3-module?
2018-02-26 18:30:07 tibbs eclipseo: Assuming it's a module and not an
application, name the SRPM and git repository python-foo and have that produce
the python3-foo subpackage.
2018-02-26 18:30:27 tibbs If it's an application, just name it "foo".
2018-02-26 18:30:28 eclipseo ok thx
2018-02-26 18:30:51 tibbs The only real exception is if python-foo
already exists as a python2-only thing and the python3 version is a separate
upstream.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component