Closed j-mracek closed 8 years ago
It is correct, this is hot fix that use private method. The code use wide range of dnf calls that is not marked as api, therefore it can be any time broken. But this information is not a secret. Therefore I can only recommend to start deeper refactoring.
Merged, Agree that in the ideal world, every thing need was in the public API, but currently that is not the case, i will use as much public API as i can and try to document the use of private api and limit it as much as possible.
If we will know that some function is externally needed, we can mark it as api or try to provide other solution (information can be passed by Bugzilla request).
@j-mracek : https://bugzilla.redhat.com/show_bug.cgi?id=1332067 would be nice to see fixed. Haven't looked deeper so there is more to come.
Ok, I am working on it.
@j-mracek : Thanks for fixing hawkey!
@genodeftest Not my work but @ignatenkobrain
@genodeftest unfortunately it's still not fixed (I just found workaround), though there is a bug in DNF itself.
@j-mracek Rather than trying to reference private APIs that have no guarantee of availability, how about actually making public APIs that programs like dnfdaemon can use for dnf 2.0?