On Thu, 3 Dec 2020, Michel Alexandre Salim wrote:
> Apart from the usual package-not-available story (which I want to
> as part of my work bringing up the EPEL Packagers SIG), my current
> snag is that python-tox-current-env uses %generate_buildrequires which
> does not work on CentOS 8:
> CentOS 8 is still on RPM 4.14:
> <mock-chroot> sh-4.4# rpm -q rpm
> I'll put up a patch to hardcode dependencies for non-Fedora releases,
> though that sorts of defeat the purpose of dynamic build
> Then again, this is only needed for EPEL8, since EPEL9 will have a
> new enough RPM.
Given that %generate_buildrequires is the selling point of pyproject-
rpm-macros, I'm guessing a better way forward for EPEL8 would be to not
require it on EPEL8 since there's no way it would work, since RH won't
Is %generate_buildrequires suppose to work for packages
which do not used python ?
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.
(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.
Andrew C. Aitchison Kendal, UK