public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schorm <mschorm@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/PyGreSQL] rawhide: [cleanup] Use %pyproject_save_files instead of manual file listing
Date: Wed, 01 Jul 2026 14:38:16 GMT [thread overview]
Message-ID: <178291669685.1.16840841980005499202.rpms-PyGreSQL-a7184b5f101c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/PyGreSQL
Branch : rawhide
Commit : a7184b5f101cf2c0baad96adcb7cac447f28aa7e
Author : Michal Schorm <mschorm@redhat.com>
Date : 2026-07-01T12:30:17+02:00
Stats : +2/-14 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/PyGreSQL/c/a7184b5f101cf2c0baad96adcb7cac447f28aa7e?branch=rawhide
Log:
[cleanup] Use %pyproject_save_files instead of manual file listing
Replace the hand-maintained list of individual module files and
dist-info entries with the %pyproject_save_files macro. This is the
canonical pattern shown in the Fedora Python Packaging Guidelines
example spec:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#_example_python_spec_file
The -l flag marks license files found in dist-info as %license
automatically, replacing the explicit dist-info/licenses/LICENSE.txt
line. The extra %license docs/copyright.rst and %doc lines remain
since they are outside the installed Python package.
%pyproject_save_files macro reference:
https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#pyproject_save_files
Co-Authored-By: Claude AI <noreply@anthropic.com>
---
diff --git a/PyGreSQL.spec b/PyGreSQL.spec
index 25086df..cf69f57 100644
--- a/PyGreSQL.spec
+++ b/PyGreSQL.spec
@@ -62,24 +62,12 @@ find -type f -exec chmod 644 {} +
%install
%pyproject_install
+%pyproject_save_files -l pg pgdb
-%files -n python3-pygresql
+%files -n python3-pygresql -f %{pyproject_files}
%license docs/copyright.rst
-%license %{python3_sitearch}/pygresql-*.dist-info/licenses/LICENSE.txt
%doc docs/about.rst docs/index.rst
-%{python3_sitearch}/pg/*.so
-%{python3_sitearch}/pg/*.py
-%{python3_sitearch}/pg/__pycache__/*.pyc
-%{python3_sitearch}/pg/py.typed
-%{python3_sitearch}/pg/_pg.pyi
-%{python3_sitearch}/pgdb/*.py
-%{python3_sitearch}/pgdb/__pycache__/*.pyc
-%{python3_sitearch}/pgdb/py.typed
-%{python3_sitearch}/pygresql-*.dist-info/WHEEL
-%{python3_sitearch}/pygresql-*.dist-info/INSTALLER
-%{python3_sitearch}/pygresql-*.dist-info/METADATA
-%{python3_sitearch}/pygresql-*.dist-info/top_level.txt
%check
reply other threads:[~2026-07-01 14:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178291669685.1.16840841980005499202.rpms-PyGreSQL-a7184b5f101c@fedoraproject.org \
--to=mschorm@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox