You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apper can show this information if the backend provides it. (E.g., the old yum backend provided it.)
The recursive case is fairly complicated (does anybody actually use that?), but the non-recursive versions should be enough for Apper. There, I would just expect a full unfiltered list of what amounts to repoquery --requires foo resp. repoquery --whatrequires --alldeps foo. The first is just a hy_package_get_requires. For the second, we need a hy_query_filter_reldep_in(…, HY_PKG_REQUIRES, hy_package_get_provides(…)).
The text was updated successfully, but these errors were encountered:
Note that Mageia's urpmi backend also supports this feature, and it would be great for it to be properly supported in the hif backend for a migration from the urpmi backend to the hif backend as the default for PackageKit in Mageia 6.
Right, I'm not against providing the functionality but I really don't really have time to write the code. If somebody does a PR I'm happy to review and commit it.
Apper can show this information if the backend provides it. (E.g., the old yum backend provided it.)
The recursive case is fairly complicated (does anybody actually use that?), but the non-recursive versions should be enough for Apper. There, I would just expect a full unfiltered list of what amounts to
repoquery --requires foo
resp.repoquery --whatrequires --alldeps foo
. The first is just ahy_package_get_requires
. For the second, we need ahy_query_filter_reldep_in(…, HY_PKG_REQUIRES, hy_package_get_provides(…))
.The text was updated successfully, but these errors were encountered: