On Tue, Mar 8, 2022 at 10:14 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote: (...) > Isn't that just a standard RPM dep solving problem, at least for > stuff inside Fedora repos or well known 3rd party add-on repos ? It is not. There's no way to query recursive BuildRequires from repository metadata in one step (basicaly because the dependency graph is bipartite). You can only do that recursively manually. > Take the minimal build root and run 'dnf install wine' and watch > what is installed to get transitive runtime deps. Similarly use > 'dnf builddep wine' to get transitive build deps. We can see > the latter from koji logs No. That's not "transitive build deps". Those are *direct* build dependencies only, and does not in turn include the BuildRequires for building those build dependencies. But those transitive BuildRequires will still need to stay around to build wine (in this example), because if they're removed, one of wine's build deps wil fail to build, and will be removed. Fabio _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
