Re: [PATCH V5 10/11] spec: Remove libvirt-daemon dependency from hypervisor subpackages
On Mon, Jan 09, 2023 at 01:19:58PM +0000, Daniel P. Berrangé wrote:
On Mon, Jan 02, 2023 at 10:26:13AM -0500, Andrea Bolognani wrote:
> * storage locking is not the default behavior and needs to be
> turned on explicitly, so it's not a big deal if part of the setup
> involves installing a couple extra packages in addition to
> editing some configuration files, and everyone else gets a leaner
> installation.
Dropping libvirt-daemon-plugin-lockd breaks the upgrade path
for people using virtlockd, as nothing will pull in the
plugin for talking to virtlockd
libvirt-daemon still depends on libvirt-daemon-plugin-lockd. In the
upgrade scenario, libvirt-daemon is already installed, so on upgrade
libvirt-daemon-plugin-lockd will be automatically dragged in. It will
only be skipped for new installations.
If you feel that the various libvirt-daemon-$hypervisor packages need
to keep providing the same exact functionality over time, then yes,
we can't drop or downgrade any of the dependencies. But, at the same
time, we're potentially breaking consumers by taking away libvirtd...
--
Andrea Bolognani / Red Hat / Virtualization