Home > Article > Backend Development > How to quickly package a new Python module
When you install an application, you are usually installing a software package that contains the application's executable code and important files such as documents, icons, etc. On Linux, software is generally packaged into formats such as RPM or DEB. Users can install it through commands such as dnf
or apt
, depending on the Linux distribution you are using. . However, new Python modules are released almost every day, so it's easy to come across a Python module that hasn't been packaged yet. This is the meaning of pyp2rpm
's existence.
Recently I was trying to install a module called python-concentration
, but the progress was not very smooth:
$ sudo dnf install python-concentration Updating Subscription Management repositories. Last metadata expiration check: 1:23:32 ago on Sat 11 Jun 2022 06:37:25. No match for argument: python-concentration Error: Unable to find a match: python-concentration
Although this is a package published on PyPi, It still cannot be packaged into an RPM package. The good news is that you can package it into an RPM package in a relatively simple process using pyp2rpm
.
First you need to set up two directories:
$ mkdir rpmbuild $ cd rpmbuild && mkdir SPECS
Install like this pyp2rpm
:
$ sudo dnf install pyp2rpm
The basis of the RPM package is a spec file. This file contains all the information you need to create this package, such as required dependencies, application version numbers, installed files and other information. When pointing to a Python module, pyp2rpm
will build a spec file for it, which you can use to create RPM packages.
The following uses python-concentration
as an example to demonstrate how to build a spec file:
$ pyp2rpm concentration > ~/rpmbuild/SPECS/concentration.spec
The following is the file it generates:
# Created by pyp2rpm-3.3.8 %global pypi_name concentration %global pypi_version 1.1.5 Name: python-%{pypi_name} Version:%{pypi_version} Release:1%{?dist} Summary:Get work done when you need to, goof off when you don't License:None URL:None Source0:%{pypi_source} BuildArch:noarch BuildRequires:python3-devel BuildRequires:python3dist(setuptools) %description Concentration [![PyPI version]( [![Test Status]( [![Lint Status]( [![codecov]( %package -n python3-%{pypi_name} Summary:%{summary} %{?python_provide:%python_provide python3-%{pypi_name}} Requires: (python3dist(hug) >= 2.6.1 with python3dist(hug) < 3~~) Requires: python3dist(setuptools) %description -n python3-%{pypi_name} Concentration [![PyPI version]( [![Test Status]( [![Lint Status]( [![codecov]( %prep %autosetup -n %{pypi_name}-%{pypi_version} %build %py3_build %install %py3_install %files -n python3-%{pypi_name} %license LICENSE %doc README.md %{_bindir}/concentration %{python3_sitelib}/%{pypi_name} %{python3_sitelib}/%{pypi_name}-%{pypi_version}-py%{python3_version}.egg-info %changelog *- 1.1.5-1 - Initial package.
To ensure that the spec file conforms to the standard, you need to use the rpmlint
command on the file:
$ rpmlint ~/rpmbuild/SPEC/concentration.spec error: bad date in %changelog: - 1.1.5-1 0 packages and 1 specfiles checked; 0 errors, 0 warnings.
It seems that the change log (%changelog
) is required Record the date.
%changelog * Sat Jun 11 2022 Tux- 1.1.5-1
Run rpmint
again:
$ rpmlint ~/rpmbuild/SPEC/concentration.spec 0 packages and 1 specfiles checked; 0 errors, 0 warnings.
Success!
You need to download the packaged code to further build the RPM package. A simple way is to parse your spec file to get the URL of the source code.
First, install spectool
through dnf
:
$ sudo dnf install spectool
Then download the source code through spectool
:
$ cd ~/rpmbuild $ spectool -g -R SPEC/concentration.spec Downloading: https://files.pythonhosted.org/...concentration-1.1.5.tar.gz 6.0 KiB / 6.0 KiB[=====================================] Downloaded: concentration-1.1.5.tar.gz
This creates a SOURCES
directory and puts the source code into it.
Now that you have verified the spec file, you can build the source software package through rpmbuild
. If you haven't installed rpmbuild
, you can also install the rpm-build
package via dnf
(or from the terminal when using the rpmbuild
command prompts for installation).
Parameter -bs
represents the build source package. Adding this parameter will produce a src.rpm file, which is a generic package for rebuilding for a specific architecture:
$ rpmbuild -bs SPECS/concentration.spec Wrote: ~/rpmbuild/SRPMS/python-concentration-1.1.5-1.el9.src.rpm
Build an installable RPM file for your system:
$ rpmbuild –rebuild SRPMS/python-concentration-1.1.5-1.el9.src.rpm error: Failed build dependencies: python3-devel is needed by python-concentration-1.1.5-1.el9.noarch
It seems that this package needs to install the Python development library to continue building. Install them to continue building. This time, the build succeeds, and more output is rendered (I've abbreviated the output here for clarity):
$ sudo dnf install python3-devel -y $ rpmbuild –rebuild SRPMS/python-concentration-1.1.5-1.el9.src.rpm [...] Executing(--clean): /bin/sh -e /var/tmp/rpm-tmp.TYA7l2 + umask 022 + cd /home/bogus/rpmbuild/BUILD + rm -rf concentration-1.1.5 + RPM_EC=0 ++ jobs -p + exit 0
Your RPM package is now built in the RPMS
subroutine directory, use dnf
to install it as usual.
$ sudo dnf install RPMS/noarch/python3-concentration*rpm
Normally we do not need to package Python modules into RPM packages. Installing modules through PyPi is also acceptable, but PyPi will install additional package managers to check and update your modules. When you use dnf
to install an RPM package, you will be able to get the complete installation list when the installation is complete. With pyp2rpm
, this process is fast, easy, and automated.
The above is the detailed content of How to quickly package a new Python module. For more information, please follow other related articles on the PHP Chinese website!