On Tue, Dec 06, 2022 at 05:15:43PM +0000, Daniel P. Berrangé wrote:
On Mon, Nov 28, 2022 at 08:33:27AM -0800, Andrea Bolognani wrote:
It appears to me that the primary reason to want this (and now virt-qemu-sev-validate) to be in a separate package is really the dependency on Python, which we understandably don't want to become a requirement for the existing libvirt-client package. So wouldn't libvirt-client-python be a more accurate and future-proof name?
That was one of the reasons, but the other was that these are just written as QEMU specific tools, and I wanted to separate them from the general purpose tools.
Suppose later we introduce a tool that's QEMU-specific but written in C, or a tool that's not specific to any hypervisor driver but written in Python. Where would those go?
In libvirt-client-qemu and (a new) libvirt-client-python respectively
Okay, I'll stick to these names in Debian then. Thanks! -- Andrea Bolognani / Red Hat / Virtualization