https://bugzilla.redhat.com/show_bug.cgi?id=1756331 --- Comment #5 from Miro Hrončok <mhroncok@xxxxxxxxxx> --- (In reply to Petr Šplíchal from comment #4) > (In reply to Miro Hrončok from comment #2) > > I'm surprised by the complexity of the %bcond options. > > > > What's the point of the Python 2 subpackage on Fedora 29? > > Unfortunately we still have a couple of tools in process of > migration to Python 3 so the Python 2 subpackage is necessary. > Hopefully soon we'll have everything Python 3 only and the spec > file will become much more simple. What tools? I don't understand why the Python 2 package is only needed in Fedora 29, but not Fedora 30. > > What's the point of using %{python3_pkgversion} if your are not > > shipping Python 3 subpackage in EL < 8? > > So the %{python3_pkgversion} is not needed any more? If you see > anything which can be simplified I'm definitely open to make it > more readable. %{python3_pkgversion} is only needed for Python 3 on EPEL 6 and 7. Clearly, the spec is designed to not build Python 3 on EPEL 6 and 7. %{python3_pkgversion} is not needed in Fedora or EPEL 8. -- 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 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
