python3 prefixed package RPMs
It seems RHEL/CentOS prefers python3-{package}.rpm as the RPM name, with the python3 part of the package name. If I add python3 as a name prefix in setuptools, it works, but it changes the egg-info directory to have the python3- prefix as well, which is not what I've seen in other python RPMs in CentOS. Is there a way I can add the python3 prefix when doing python3 setup.py bdist_rpm? Thanks. --John
On Thu, 9 Jan 2020 at 07:00, Ratliff, John <jdratlif@iu.edu> wrote:
It seems RHEL/CentOS prefers python3-{package}.rpm as the RPM name, with the python3 part of the package name. If I add python3 as a name prefix in setuptools, it works, but it changes the egg-info directory to have the python3- prefix as well, which is not what I’ve seen in other python RPMs in CentOS.
Is there a way I can add the python3 prefix when doing python3 setup.py bdist_rpm?
The short answer is "No", as Fedora/RHEL/EPEL/CentOS RPMs aren't built that way. The longer answer is to not use bdist_rpm, and instead use an RPM skeleton generator like pyp2rpm: https://github.com/fedora-python/pyp2rpm That was originally written by some of the Python package maintainers at Red Hat, so the Fedora RPM template is pretty good. Alternatively, if the project you're making RPMs for is open source, you may want to take a look at Fedora's COPR service: https://docs.pagure.org/copr.copr/screenshots_tutorial.html#screenshots-tuto... There's a "PyPI" source option that will download the artifacts from PyPI, run pyp2rpm, and create the RPM and repo for you from that. If you do decide to go down that path, then https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproje... would be the best place to contact for more info/assistance. Cheers, Nick. -- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia
participants (2)
-
Nick Coghlan
-
Ratliff, John