On 12/2/20 8:00 AM, Miroslav Suchý wrote:
Dne 01. 12. 20 v 13:07 Pavel Raiskup napsal(a):
I'm pleased to announce that there's a new Mock release. Except for
several bugfixes, this release introduces a new
"External Build Requires" feature (by Miroslav Suchý)
I want to ask you for feedback on this feature.
https://github.com/rpm-software-management/mock/wiki/Feature-external-deps
This feature will allow you to use in SPEC file
BuildRequires: external:pypi:foo
which will run
pip3 --install foo
in the buildroot.
This is a new and experimental feature. Not yet enabled in Mock by default. And I do **not** expect that it will be
enabled in Fedora. Ever. It may be enabled in Copr one day. The primary audience is 3rd party packagers who need some
library for building, and it is not available as RPM.
I am aware that this is breaking some fundamentals of RPM. For this reason, I want to hear the feedback on whether this
is interesting for you or it should die in agony.
I can imagine myself using this locally when some test dependencies are missing
(e.g. in RHEL). I hope it's possible to use this with `mock --install` and not
just as BuildRequires. It is not clear from the linked GH wiki page.
Right now, this feature supports PyPI - I am confident there.
I have two questions about the PyPI support.
1) Can I specify version ranges? Do I use RPM or Python syntax?
2) I've read that a temporary RPM package is created:
> To satisfy rpm dependencies Mock calls create-fake-rpm and creates a fake rpm
> package that provides external:pypi:foo and installs it in chroot.
Does the fake RPM provide pytohn3.9dist(foo)? Should it?
--
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
