On Fri, 2020-02-28 at 23:06 +0100, Miro HronĨok wrote:
> I assume there's an extra "not" here. On that assumption - I
understand
> the problem, but if you check the history of my builds in EPEL, I'm
> definitely not in that group of people :P
Cool, sorry for that assumption, it sounded like not being available on EPEL is
a show stopper.
It just makes things more complicated, as usual...
A follow-up observation, btw: can we exclude things from
pyproject_buildrequires ? (whether that's done at the level of the
dynamic build generation process itself, or within the pyproject
macro/tool I don't care - but I couldn't find any docs indicating it's
possible at either level so far).
I use setuptools-git for most of my projects. So in pyproject.toml I'm
putting this:
requires = ["setuptools>=40.6.0", "setuptools-git",
"wheel"]
because setuptools-git is needed *to produce the source distribution*,
thus it is a 'requires' so far as PEP-517/518 are concerned. However,
it's not a BuildRequires for a Fedora package, because a Fedora package
build *starts* from the source distribution. It doesn't need to produce
one.
I think I ran into an earlier version of this problem when I tried to
use setup_requires briefly, or something. It'd be nice to use
pyproject_buildrequires, but it'd also be nice for it not to pull in
something that isn't actually needed...
another thing I just ran into while trying this stuff out:
https://bugzilla.redhat.com/show_bug.cgi?id=1808601
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net