Re: [libvirt] [PATCH 00/10] Enable loadable modules for libvirtd

["Daniel P. Berrange" <berrange redhat com>]

On Tue, Apr 03, 2012 at 09:57:19PM +0800, Daniel Veillard wrote:
> On Tue, Apr 03, 2012 at 02:08:11PM +0100, Daniel P. Berrange wrote:
> > So, 'yum install libvirt' would end up pulling in every single hypervisor
> > we support (qemu, qemu-kvm, xen), which is not at all what we want.
> > 
> > Separating the libvirt-daemon-XXX packages from the libvirt-daemon-driver-XXX
> > packages is key to achieving the goal of minimising install footprint, while
> > maintaining backwards compatibility with existing RPM deps.
> 
>   I still wonder if it is worth it then. Adding an extra empty rpm just
> for the sake or avoiding a explicit hypervisor dependency at the
> application level. The whole scheme adds N + 1 empty rpms just for
> avoiding that dep that the application need to explicitely state right
> now anyway.

I think it is worth it, based on the fact that we get reasonably
frequent bug reports that installing libvirt did not install qemu-kvm,
or similar. Also, it avoids the need for applications to care about
the different package names - eg in RHEL-5 the RPM was 'kvm', while
in RHEL-6, the RPM was 'qemu-kvm', and who knows if it will change
again...

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|