Re: BuildRequires on python-abi

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

 



seth vidal wrote:
To give you a bit more info:
 - mach reads the buildreqs from the srpms - and tries to satisfy them

This step is just plain wrong. This is prone to breaking in several scenarios including this one. We need deps to be parsed only from a fresh spec, parsed within a minimal buildroot of a target distro.

http://enrico-scholz.de/fedora.us-build/files/
IIRC Enrico's wrappers around mach used in the fedora.us buildsystem had two passes for spec parsing to pull in deps. This older implementation is not ideal because it avoided rpmlib. But this multiple pass approach using rpmlib is exactly the right idea.

First pass allows it to determine BuildRequires to put into the buildroot. Then after those BuildRequires are installed, the second pass happens during rpmbuild itself, where the actual values from stuff executed in %() are filled in the resulting packages. The deps in the binary RPMS are the only important deps. The deps in the SRPM output are unimportant and should not influence anything in the future.

Warren Togami
wtogami@xxxxxxxxxx


[Index of Archives]     [Fedora Users]     [Fedora Development]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux