docs: Don't BuildRequire these macros in Fedora and EPEL 9
`python3-devel` already requires `pyproject-rpm-macros` in Fedora and EPEL 9. Update the usage docs to reflect this. Related: rhbz#1950291 Signed-off-by: Hunor Csomortáni <csomh@redhat.com>
This commit is contained in:
parent
2abd0036ea
commit
3f5f8e46c1
14
README.md
14
README.md
@ -23,15 +23,17 @@ These macros replace `%py3_build` and `%py3_install`, which only work with `setu
|
||||
Usage
|
||||
-----
|
||||
|
||||
To use these macros, first BuildRequire them:
|
||||
To use these macros, first BuildRequire the devel package for the Python you
|
||||
are building against. In Fedora, that's `python3-devel`.
|
||||
|
||||
BuildRequires: python3-devel
|
||||
|
||||
The macros will be pulled in as a dependency on Fedora and EPEL 9+.
|
||||
In other distributions you need to BuildRequire the macros as well:
|
||||
|
||||
BuildRequires: python3-devel
|
||||
BuildRequires: pyproject-rpm-macros
|
||||
|
||||
Also BuildRequire the devel package for the Python you are building against.
|
||||
In Fedora, that's `python3-devel`.
|
||||
(In the future, we plan to make `python3-devel` itself require
|
||||
`pyproject-rpm-macros`.)
|
||||
|
||||
Next, you need to generate more build dependencies (of your projects and
|
||||
the macros themselves) by running `%pyproject_buildrequires` in the
|
||||
`%generate_buildrequires` section:
|
||||
|
Loading…
Reference in New Issue
Block a user