| |
@@ -28,6 +28,7 @@
|
| |
- the proper files are installed in the proper places
|
| |
- module glob in %%pyproject_save_files (some modules are included, some not)
|
| |
- combined manual and generated Buildrequires
|
| |
+ - building an extension module via %%pyproject_buildrequires -w
|
| |
|
| |
|
| |
%package -n python3-ldap
|
| |
@@ -48,11 +49,13 @@
|
| |
|
| |
|
| |
%generate_buildrequires
|
| |
- %pyproject_buildrequires -t
|
| |
+ # -w is not required with this package, but we test that we can use it anyway
|
| |
+ %pyproject_buildrequires -t -w
|
| |
|
| |
|
| |
%build
|
| |
- %pyproject_wheel
|
| |
+ #%%pyproject_wheel -- this is done via %%pyproject_buildrequires -w
|
| |
+
|
| |
# Internal check that we can import the built extension modules from %%{pyproject_build_lib}
|
| |
%{python3} -c 'import _ldap' && exit 1 || true
|
| |
PYTHONPATH=%{pyproject_build_lib} %{python3} -c 'import _ldap'
|
| |
churchyard
commented 2 years ago
When extension modules are built in %pyproject_buildrequires,
we need to create the package note file.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2097535
This is tested via python-ldap -- %pyproject_buildrequires -w fails without the fix.
Neither python-markupsafe nor python-mistune can be used as a test
because they only warn when the extension module cannot be built
because they fallback to pure Python.