Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hif: RFE: Implement dependency querying (pk_backend_depends_on, pk_backend_required_by) #106

Open
kkofler opened this issue Feb 2, 2016 · 3 comments · May be fixed by #495
Open

hif: RFE: Implement dependency querying (pk_backend_depends_on, pk_backend_required_by) #106

kkofler opened this issue Feb 2, 2016 · 3 comments · May be fixed by #495

Comments

@kkofler
Copy link
Collaborator

kkofler commented Feb 2, 2016

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(…)).

@Conan-Kudo
Copy link
Member

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.

@hughsie
Copy link
Collaborator

hughsie commented Feb 2, 2016

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.

@Conan-Kudo
Copy link
Member

I started trying to implement this a while ago in #495, I'm hoping I can get this implemented soon...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants