On 12/3/20 10:06 PM, Andrew C Aitchison wrote:
Is %generate_buildrequires suppose to work for packages
which do not used python ?
Yes, see https://fedoraproject.org/wiki/Changes/DynamicBuildRequires
From the name I would expect it to, but reading that doc makes me
think %generate_buildrequires *is* python specific.
If so, the name is misleading.
When you read the docs at
https://src.fedoraproject.org/rpms/pyproject-rpm-macros that is indeed Python
specific. It describes the following:
%generate_buildrequires
%pyproject_buildrequires
But you can heve many other things, e.g.:
%generate_buildrequires
echo fruit-cake
Or:
%generate_buildrequires
%cargo_generate_buildrequires
(I am also confused/suspicious of the point of a macro to automate
build requires, except as a step on a path to somewhere else.
If build requirements need to be stated explicitly,
then automating their statement is a good way of hiding an issue
that needs to be reviewed whenever changes are made.
)
Indeed, things are less explicit when reading the spec file.
OTOH When upstream requirements change, one does not need to update them
manually. No more obsolete buildrequires (they tend to happen, really).
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
