From: "Sandro Bonazzola" <sbonazzo(a)redhat.com>
To: "Federico Simoncelli" <fsimonce(a)redhat.com>, "Dan
Kenigsberg" <danken(a)redhat.com>
Cc: devel(a)ovirt.org, dougsland(a)redhat.com, "Sven Kieske"
<s.kieske(a)mittwald.de>, "users" <users(a)ovirt.org>
Sent: Wednesday, September 24, 2014 9:00:20 AM
Subject: Re: Building vdsm within Fedora
Il 24/09/2014 08:53, Federico Simoncelli ha scritto:
> ----- Original Message -----
>> From: "Dan Kenigsberg" <danken(a)redhat.com>
>> To: "Sandro Bonazzola" <sbonazzo(a)redhat.com>, devel(a)ovirt.org,
>> fsimonce(a)redhat.com, dougsland(a)redhat.com
>> Cc: "Sven Kieske" <s.kieske(a)mittwald.de>, "users"
<users(a)ovirt.org>
>> Sent: Tuesday, September 23, 2014 11:21:18 PM
>> Subject: Building vdsm within Fedora
>>
>> Since Vdsm was open-sourced, it was built and deployed via
>> Fedora.
>>
>> Recently [
http://gerrit.ovirt.org/31214] vdsm introduced a spec-file
>> dependency onf qemu-kvm-rhev, and considered to backport it to the
>> ovirt-3.4 brach.
>>
>> Requiring qemu-kvm-rhev, which is not part of Fedora's EPEL6 branch,
>> violates Fedora's standards.
>>
>> So basically we have two options:
>>
>> 1. Revert the qemu-kvm-rhev dependency.
>> 2. Drop vdsm from EPEL6 (or completely from Fedora); ship Vdsm only
>> within the oVirt repositories.
>>
>> A third option would be to have one rpm, with qemu-kvm-rhev, shipped in
>> ovirt, and another without it - shipped in Fedora. I find this overly
>> complex and confusing.
>
> I think that until now (centos6) we were using qemu-kvm/qemu-img in the
> spec file and then the ovirt repository was distributing qemu-*-rhev
> from:
>
>
http://resources.ovirt.org/pub/ovirt-3.4-snapshot/rpm/el6/x86_64/
>
> It this not possible with centos7? Any problem with that?
We're shipping qemu-kvm-rhev on 3.4, 3.5 and master for EL6 and EL7.
The issue is that if you don't enable ovirt, epel fails repository closure.
You probably missed the first part "we were using qemu-kvm/qemu-img in
the spec file". In that case you won't fail in any requirement.
Basically the question is: was there any problem on centos6 before
committing