[ovirt-devel] Building vdsm within Fedora
Sandro Bonazzola
sbonazzo at redhat.com
Wed Sep 24 07:00:20 UTC 2014
Il 24/09/2014 08:53, Federico Simoncelli ha scritto:
> ----- Original Message -----
>> From: "Dan Kenigsberg" <danken at redhat.com>
>> To: "Sandro Bonazzola" <sbonazzo at redhat.com>, devel at ovirt.org, fsimonce at redhat.com, dougsland at redhat.com
>> Cc: "Sven Kieske" <s.kieske at mittwald.de>, "users" <users at 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.
>
> I find being in fedora a way to keep the spec file and the rpm updated
> and as clean as possible.
>
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
More information about the Devel
mailing list