Marek Blaha

The split was a result of the fix for issue https://github.com/rpm-software-management/dnf5/issues/1633 . We will discuss the decision on the next dnf team meeting.

There are several options that influence which weak dependencies will be installed: `exclude_from_weak` - This allows the user to specify a list of packages they do not wish to install...

> Well the openSUSE repositories naturally already have such metadata, is openSUSE support something you care about? (Because I'm actually using openSUSE, and dnf5 annoyingly doesn't support it's concept of...

Hi, for the `repoquery` command you can use the `--latest-limit=1` for this purpose. This way the command will return only the highest available version for each architecture. Maybe we can...

> I'm not against other command to respect --best. The only problem I have with it is that it would break compatibility. E.g `dnf download` now downloads all architectures. Contrary...

Hi, the method call accepts one parameter, and returns two values - the resolved transaction in transaction_items and the overall result. Note the direction="in" and direction="out" in the xml.

I recall a situation involving mandatory packages in groups that were specific to certain architectures and did not exist on other arches (see https://bugzilla.redhat.com/show_bug.cgi?id=1427365#c5). If I remember correctly, the issue...

Regarding outputs, offline transactions use their own `PlymouthTransCB` transaction callbacks, which currently seem to only notify the user about `elem_progress` events. You're right that scriptlets can take a disturbingly long...

> * Instead of rebooting from a deep of dnf5, throw a special exception, let unwind the stack and happen all desctructors and catch it from the main() top-most try-catch...

But that would be the API change and you would need to change all the commands `run()` method to return the flag. Maybe adding `Context::set_reboot_requested()` method and storing the flag...