Closed xsuchy closed 8 years ago
pyp2rpm pyflakes generates following %files section
%files -n python2-%{pypi_name}
%doc README.rst LICENSE
%{_bindir}/pyflakes
%{_bindir}/pyflakes-2
%{_bindir}/pyflakes-%{python2_version}
%{python2_sitelib}/%{pypi_name}
%{python2_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info
%files -n python3-%{pypi_name}
%doc README.rst LICENSE
%{_bindir}/pyflakes-3
%{_bindir}/pyflakes-%{python3_version}
%{python3_sitelib}/%{pypi_name}
%{python3_sitelib}/%{pypi_name}-%{version}-py?.?.egg-info
result of --srpm option can be successfully built and the content of rpms is alright. I can install both to my system without any errors.
It seems that pyflakes-1.2.3-1.fc25.noarch is package from fedora repositories http://koji.fedoraproject.org/koji/buildinfo?buildID=762537, name of the package generated by pyp2rpm would be python2-pyflakes-1.2.3-1.fc25.noarch.
python3 subpackage contains binary called foo (/usr/bin/pyflakes in this case) only if it is generated using -b3 option. I am not sure if this is the best behavior but it doesn't violate the guidelines if I understand them correctly.
@xsuchy @hroncok Is current behavior that I explained above correct? Do you suggest some changes here?
Hmm, while it does not satisfy my needs completely and it will cause me some problems, I agree that it is on pair with guideliness and I will need to live with that. So closing.
This will create python2 and python3 subpackage. And both contains /usr/bin/pyflakes. Which will result in conflicts if you want to install both (e.g. as buildrequires).
I think pyp2rpm should somehow try to address it.