-
Notifications
You must be signed in to change notification settings - Fork 16
Choice weak dependencies #45
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
base: master
Are you sure you want to change the base?
Choice weak dependencies #45
Conversation
Before the modification, this function represents 35% of the time spent in get_packages. After, it is just 30%
…on, size and group This give an important improvement in time of GetPackages at start of application and relaod. Gain is about 20% of the period of loading cache.
…install packages: normal dependencies and weak dependencies Thus in dnfdragora, the weak dependencies can be displayed separately (see issue #185). An entry 'install_weak' is added in the package disctionnary.
@papoteur-mga can you please rebase this PR on top of master, so it only contains the weak dependencies in transaction changes. |
Breaking the API of dnfdaemon is fine, as we haven't declared a stable API yet. The only other consumer right now is dnfdragora, and we're okay to change it as dnfdaemon changes. |
@timlau do you think we can have a talk about dnfdaemon and (dnf) API, dnfdragora and yumex-dnf it would be great if we could work together on these projects, wdyt? |
@anaselli fine with me,feel free to mail me. |
Provides the list of package of a transaction with distinction in to install packages: normal dependencies and weak dependencies
Thus in dnfdragora, the weak dependencies can be displayed separately (see issue #185). An entry 'install_weak' is added in the package dictionnary.
I don't understand why the pull request is not only about the last commit. Surely not clean.