On 2023-01-19 09:48, Daniel P. Berrangé wrote:
The idea is that an application will put a dep on the specific libvirt-daemon-driver-XXX that its functionality requires. If Boxes requires storage APIs, then add a Requires: libvirt-daemon-driver-storage-core, along with any of the storage backends Boxes uses.
It looks like there are currently ~ 13 packages that currently require libvirt or libvirt-daemon-kvm that would need review and possibly adjustment, and I'm willing to do that work, but I have to ask: How likely is it that "fedora-comps" would accept a PR that narrows the libvirt package set in the "virtualization" and "virtualization-headless" groups?
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
