Re: Tox automation in packaging macros

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 28. 02. 20 23:36, Adam Williamson wrote:
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).

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.

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

Keep them coming \o/

--
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux