> >> On Fri, Jul 08, 2016 at 10:49:57AM +0100, Daniel P.
Berrange wrote:
> >> > If we can't build edk2 x86_64 bios blob on aarch64, and can't
import
> >> > the previously built noarch packages, then seems to say the only
> >> > option left is to split the edk2 package into two source packages.
> >> > One that exclusively builds the BIOS blobs (and can be entirely
> >> > noarch), and one that builds the host tools (which is arch dependant).
> >> > It rather sucks that build system limitations would force us to split
> >> > the source RPM in this way though :-(
> >>
> >> The alternative might be to reduce the hard Requires dependency
> >> to either Recommends or Suggests. What do you think about that?
> >
> > I'm not a huge fan of that, because I think it is desirable for apps
> > to be able to presume EFI support is available out of the box if QEMU
> > is installed. Making it optional will just leave to user bug reports
> > when trying to use EFI in virt-manager and it failing due to missing
> > BIOS.
> >
> > Though as a short term hack, I guess I'd be ok with making it Recommends
> > on aarch64 only, and leaving it as Requires on all other arches, with a
> > view to making it Requires again on aarch64 once we have a better fix.
>
> It's also an issue when building libguestfs on ppc.koji and presumably
> s390.koji due to qemu-system-x86
>
> DEBUG util.py:421: Error: nothing provides edk2-ovmf needed by
> qemu-system-x86-2:2.6.0-4.fc25.ppc64
>
>
http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=3518487
Ok, lets rephrase that. I'd be fine with having Requires on x86_64
and Recommends on all other arches for edk2-ovmf, on the basis that
99% of users will be using ovmf on x86_64 hosts with KVM. The number
of people wanting to use ovmf with QEMU on non-x86_64 is likely single
digits.
Works for me except for aarch64 on aarch64 where it would be good to
have it a hard dep as well