Why does so much virt stuff depend on glusterfs?

Cole Robinson crobinso at redhat.com
Wed Jul 24 17:39:14 UTC 2013


On 07/24/2013 01:36 PM, Cole Robinson wrote:
> On 07/24/2013 05:18 AM, Daniel P. Berrange wrote:
>> On Tue, Jul 23, 2013 at 11:28:20AM -0700, Adam Williamson wrote:
>>> On Tue, 2013-07-23 at 18:15 +0100, Richard W.M. Jones wrote:
>>>> On Tue, Jul 23, 2013 at 12:57:50PM -0400, Dave Jones wrote:
>>>>> On Mon, Jul 22, 2013 at 05:17:01PM -0700, Adam Williamson wrote:
>>>>>  
>>>>> So this thread is complaining about..
>>>>>
>>>>>  > > Removing:
>>>>>  > >  glusterfs                       x86_64 3.4.0-2.fc19     @updates-testing 4.7 M
>>>>>  > > Removing for dependencies:
>>>>>  > >  glusterfs-api                   x86_64 3.4.0-2.fc19     @updates-testing  88 k
>>>>>  > >  glusterfs-fuse                  x86_64 3.4.0-2.fc19     @updates-testing 233 k
>>>>>
>>>>> < 5M of deps, meanwhile..
>>>>>
>>>>>  > >  qemu-system-alpha               x86_64 2:1.4.2-4.fc19   @updates-testing 4.1 M
>>>>>  > >  qemu-system-arm                 x86_64 2:1.4.2-4.fc19   @updates-testing 5.2 M
>>>>>  > >  qemu-system-cris                x86_64 2:1.4.2-4.fc19   @updates-testing 2.8 M
>>>>>  > >  qemu-system-lm32                x86_64 2:1.4.2-4.fc19   @updates-testing 2.8 M
>>>>>  > >  qemu-system-m68k                x86_64 2:1.4.2-4.fc19   @updates-testing 3.8 M
>>>>>  > >  qemu-system-microblaze          x86_64 2:1.4.2-4.fc19   @updates-testing 5.6 M
>>>>>  > >  qemu-system-mips                x86_64 2:1.4.2-4.fc19   @updates-testing  21 M
>>>>>  > >  qemu-system-or32                x86_64 2:1.4.2-4.fc19   @updates-testing 2.7 M
>>>>>  > >  qemu-system-ppc                 x86_64 2:1.4.2-4.fc19   @updates-testing  18 M
>>>>>  > >  qemu-system-s390x               x86_64 2:1.4.2-4.fc19   @updates-testing 3.1 M
>>>>>  > >  qemu-system-sh4                 x86_64 2:1.4.2-4.fc19   @updates-testing 7.5 M
>>>>>  > >  qemu-system-sparc               x86_64 2:1.4.2-4.fc19   @updates-testing 7.3 M
>>>>>  > >  qemu-system-unicore32           x86_64 2:1.4.2-4.fc19   @updates-testing 2.7 M
>>>>>  > >  qemu-system-xtensa              x86_64 2:1.4.2-4.fc19   @updates-testing 5.6 M
>>>>>
>>>>> Do we really *need* all those ?
>>>>
>>>> Hopefully those *are* removable.
>>>>
>>>> Unfortunately some packages depend on the 'qemu' meta package which
>>>> pulls in all of the emulators.
>>>
>>> I don't know if that's the case for me, I just did a 'yum install
>>> @Virtualization' on the host in question which is why I have all the
>>> stuff the metapackages pull in. I know about that, which is why I didn't
>>> complain about it.
>>
>> Hmm, if @Virtualization pulls in all the QEMU emulators then we probably
>> have a bogus comps config. I'd say @Virtualization should probably only
>> pull in the KVM binary, leaving the QEMU emulators alone, since few
>> people will want them.
>>
> 
> Yeah comps still has a dep on plain 'libvirt' which will pull all of that in.
> If no one objects, I'll push a change to make it libvirt-daemon-driver-kvm
> which should only pull in the required libvirt bits.

Err, s/libvirt-daemon-driver-kvm/libvirt-daemon-kvm/

- COle



More information about the devel mailing list