kolage

Please also include information about how the existing dnf4 automatic configuration files can be migrated to the dnf5 layout.

OK, I believe we can proceed with merging this to main.

> Do you think we have sufficient API coverage for me to implement a PackageKit backend using libdnf5 based on what we have for the current dnf backend? https://github.com/PackageKit/PackageKit/tree/main/backends/dnf I...

> Do you think we have sufficient API coverage for me to implement a PackageKit backend using libdnf5 based on what we have for the current dnf backend? https://github.com/PackageKit/PackageKit/tree/main/backends/dnf So,...

> We (the [mock](https://github.com/rpm-software-management/mock) utility upstream) are interested in having something like this natively supported by DNF. For the time being, we'll generate a custom lockfiles per [this schema](https://github.com/rpm-software-management/mock/blob/main/mock/docs/buildroot-lock-schema-1.0.0.json) for...

A new approach for implementing this feature in dnf5 needs to be designed. There is an API [prepared](https://github.com/rpm-software-management/dnf5/blob/5.1.17/libdnf5/rpm/transaction.hpp#L92) in the `RpmProblem` class that connects to rpm's `rpmProblemGetDiskNeed` method, but it's...

Related issue: https://github.com/rpm-software-management/dnf5/issues/326.

I tested this a bit, and here are my thoughts: - The 80-column output is better than the current state in the main branch. - If there's a hard-coded limit...

This is a complex topic, and not everyone will be satisfied. Our team discussed this and agreed to make minimal changes to the current default transaction table layout. For now,...

Related issue to the mentioned ABI break: https://github.com/rpm-software-management/dnf5/issues/1025.