On 29. 05. 24 9:48, Karolina Surma wrote:
Hi Felix,
The missing bit is whether the build backend of pypdf exposes the metadata that
pyproject-rpm-macros use to detect the license file.
pypdf uses flit-core as its build backend which doesn't implement
`License-File` field (it's a part of PEP 639, still in draft and implemented
only in a subset of build backends, like setuptools and hatch). Hopefully in
the future it'll become a standard.
For now, you've got to declare the license file via the %license macro manually.
See "Generating the %files section" of
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/blob/rawhide/f/README.md for more details.
Most importantly, this paragraph:
"""
%pyproject_save_files can automatically mark license files with %license macro
and language (*.mo) files with %lang macro and appropriate language code. Only
license files declared via PEP 639 License-File field are detected. PEP 639 is
still a draft and can be changed in the future. It is possible to use the -l
flag to declare that a missing license should terminate the build or -L (the
default) to explicitly disable this check. Packagers are encouraged to use the
-l flag when the %license file is not manually listed in %files to avoid
accidentally losing the file in a future version. When the %license file is
manually listed in %files, packagers can use the -L flag to ensure future
compatibility in case the -l behavior eventually becomes a default.
"""
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
