Re: qemu on i686

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Feb 28, 2023 at 10:52:06AM +0000, Richard W.M. Jones wrote:
> [Only direct dependencies]
> Packages that BuildRequire qemu*:
> 
> [n] appliance-tools
>     cloud-utils
> [n] cockpit-machines
> [n] containers-common
>     copr-rpmbuild
> [n] diskimage-builder
>     guestfs-tools
> [n] imagefactory-plugins
>     kata-containers
>     kiwi
> [n] kiwi-boxed-plugin
> [ns]koji
>     libguestfs
>     libvirt
> [n] libvirt-test-API
> [s] lorax
> [n] nodepool
> [n] openqa
>     os-autoinst
> [n] osbuild
> [x] osbuild-composer
> [x] qemu-sanity-check
>     qt-virt-manager
> [n] ravada
> [n] standard-test-roles
> [n] virt-backup
>     virt-v2v
>     virtiofsd
>     xen
> 
>         key: [n] = noarch
>              [s] = dependency limited to a subpackage
>              [x] = already excludearch i686
> 
> Packages that BuildRequire libvirt*:
> 
> [n] cockpit-machines
> [s] collectd
>     condor
> [ns]fence-agents
>     gnome-boxes
>     guestfs-tools
>     libguestfs
>     libvirt-cim
>     libvirt-dbus
>     libvirt-designer
>     libvirt-glib
> [n] libvirt-java
>     libvirt-python
>     libvirt-sandbox
> [n] libvirt-test-API
> [n] mom
>     nbdkit
>     ocaml-libvirt
> [n] oz
> [s] pcp
>     perl-Sys-Virt
>     perl-Sys-Virt-TCK
>     php-libvirt
>     qt-virt-manager
> [n] ravada
>     rubygem-ruby-libvirt
>     sblim-gather
> [s] systemtap
> [n] testcloud
> [n] tmt
>     vhostmd
>     virt-bootstrap
> [n] virt-lightning
> [n] virt-manager
>     virt-top
>     virt-v2v
>     virt-viewer
> 
> It seems plausible that we would still ship libvirt.i686, but remove
> the qemu-related subpackages (leaving, essentially, only the libvirt
> client bindings).  In which case the second list can be largely ignored.

Yes, my intent would be to disable build of the libvirt-daemon-driver-qemu,
libvirt-daemon-qemu and libvirt-daemon-kvm sub-RPMS on i686. This would
leave the libvirt clients and most expecially the -devel package. So I
think we can ignore stuff with a BuildRequires on libvirt(-devel).

What would matter is anything with a Requires on the QEMU related
libvirt sub-RPMs directly.

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux