That wouldn't setup the other dependencies the macro controls, for example:
echo 'python3dist(pip) >= 19'
For toml projects:
echo '(python3dist(tomli) if python3-devel < 3.11)'
For setup.py:
echo 'python3dist(setuptools) >= 40.8'
That's what I meant with the macro having a way to just pass an
argument to tell it to generate the corresponding dependencies
without checking for the existence of the file.
I can just add that those manually before the macro.
Thank you,
Carlos R.F.
On 8/20/25 12:33 AM, Miro Hrončok
wrote:
On 20. 08. 25 6:15, Carlos Rodriguez-Fernandez wrote:
I see, /usr/lib/rpm/redhat/pyproject_buildrequires.py really expects the project files already generated.
Perhaps, the macros should allow some argument to tell it to "not run the detection logic, and just do its best for the kind of project" and let the maintainer define the additional build requires? These projects with .in files appears to be mainly python bindings with little to no py dependencies anyways.
Well, yes?
%pyproject_buildrequires -N
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
