On Tue, 8 Mar 2022 09:40:16 +0000 Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote: > On Tue, Mar 08, 2022 at 10:30:33AM +0100, Fabio Valentini wrote: > > 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. > > Oh yes, I simplified the build deps problem too much. Still > feels like a task that is ripe for machine automation. I have to check my scripts' collection, but I think I had something to "compute" the transitive deps ... Dan > As written the proposal is effectively asking every maintainer to > dep solve the build deps manually in their head to see if their > pacakge is still needed by something. IMHO that is inevitably going > to lead to mistakes and puts unnecessary burden on individual > maintainers. > > With regards, > Daniel > -- > |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| > |: https://libvirt.org -o- https://fstop138.berrange.com :| > |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| > _______________________________________________ > 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 _______________________________________________ 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
