Jaroslav Mracek

Here is an alternative solution mentioned by Petr Pisar above - Reject `=` with short options - https://github.com/rpm-software-management/dnf5/pull/1442.

@jrohel I understand your point and I am not pushing any solution. I have one very strong concern - the change of behavior is silent therefore very difficult to discover....

What about to only extend message and include IDs of repositories, because as it was mentioned skipping is not per package property, but per repository including commandline repository. What about...

@bowlofeggs What kind of API do you search for? Python, C, C++?

@bowlofeggs I believe that there is a small misunderstanding. python-hawkey is replaced by python-dnf. API that is well described (https://dnf.readthedocs.io/en/latest/api.html). API of libdnf is under development and will be also...

In our future project libdnf-5/dnf-5 we have a plan to also provide go bindings. The work can be found in dnf-5-devel branch. If you want to get specific information about...

With present API it is possible to get everything what you need, but only in python, and C.

@abitrolly May I ask you whether you need C++ or a Python code?

I am suggesting that `dnf5 history redo` should be implemented by a way that will resolve this use-case. I don't see any benefit in `redo` implementation that has very limited...

> However, I believe that DNF5 should not deny users from performing a dependency resolution which happens before the transaction check. Querying DNF5 for action it would perform, in a...