On Fri, 4 Dec 2020, Miro Hrončok wrote:
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
Thanks. Now that I read that, this looks like a good plean.
(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.
Certainly a very good step in this direction.
Is there anything to save an upstream devel from having to know that, say,
what Ubuntu calls "libX11-dev", CentOS calls libX11-devel ?
No more obsolete buildrequires (they tend to happen, really).
Yes; I have seen that.
Thanks for the pointer to
https://fedoraproject.org/wiki/Changes/DynamicBuildRequires
--
Andrew C. Aitchison Kendal, UK
andrew@xxxxxxxxxxxxxxx
_______________________________________________
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
