On Mon, 2007-02-26 at 00:07 +0100, Karel Zak wrote: > On Sun, Feb 25, 2007 at 08:48:12PM +0000, Daniel P. Berrange wrote: > > See this thread on kvm-devel for a question about link time dependancies > > in libvirt. I'm not sure what the optimal approach is for us to deal with > > this is - just something we should think about in an idle moment... > > Definitely (... it would be best for FC7, no later.) > > The libvirt already uses exactly defined API (struct virDriver). I > think it's a possible food for dlopen(). The rpm could be divided to > multiple subpackages: > > libvirt.rpm > libvirt-driver-xen.rpm > libvirt-driver-qemu.rpm > libvirt-driver-kvm.rpm >From a packaging point of view, this seems like the sanest approach; note though that somebody (hopefully not the user) has to jump through some hoops to make sure that their installed libvirt drivers match their installed virt infrastructure. One way to do that would be to make the xen (or kernel-xen ?) package depend on libvirt-driver-xen etc. David