On 28. 02. 20 23:49, Miro Hrončok wrote:
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).
You can patch/sed/etc. upstream metadata in %prep. The original idea is that if
upstream metadata is wrong, it should be fixed in upstream, not in spec.
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 see the problem, but I don't see a nice solution.
What about this?
%generate_buildrequires
%{pyproject_buildrequires -t} | grep -v setuptools-git
https://src.fedoraproject.org/rpms/pyproject-rpm-macros/pull-request/35
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
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
