[fedora-virt] Should python-virtinst %require libvirt?

Daniel P. Berrange berrange at redhat.com
Thu Oct 8 15:49:17 UTC 2009


On Thu, Oct 08, 2009 at 11:44:38AM -0400, James Laska wrote:
> Greetings,
> 
> Quick question about virt package dependencies.  The Rawhide Acceptance
> Install Test (which does a virt install) [1] first installs the required
> packages by doing:
> 
>   # yum -y install qemu-kvm python-virtinst pax
> 
> It seems that installing python-virtinst used to also pull libvirt into
> the transaction.  However, this is no longer the case [2].  Should the
> deps chain when installing python-virtinst also install libvirt?  Or is
> it expected that if you wish to run your own virt daemon, you should
> install libvirtd?

In previous Fedora:

  python-virtinst -> libvirt-python
  libvirt-python -> libvirt  (and thus libvirtd)

In F12 though we split libvirt 

   python-virtinst -> libvirt-python
   livirt-python -> libvirt-client


So, python-virtinst no longer causes the libvirtd daemon to be pulled in

In the general case this is good, because we explicitly want to allow a
client only install of virtualization tools.

If wanting to actually setup a virtualization host though, your yum 
command line is no longer sufficient.

You probably want to change to use

   yum -y groupinstall  Virtualization

Which I believe should pull in KVM, libvirt, virt-manager & virtinst


Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|




More information about the virt mailing list