On Thu, Nov 20, 2014 at 12:36:20PM +0100, Sven Kieske wrote: > > > On 20/11/14 12:18, Dan Kenigsberg wrote: > > RHEV cannot depend on EPEL. If a package is not in RHEL, RHEV must > > consume it, which is something that's not worth doing in this case > > (where there's not functional benefit). > > As I said: it already does that: > > an excerpt from the latest ovirt-release35-001-1.noarch.rpm: > in /./usr/share/ovirt-release35/ovirt-el6-deps.repo > you find: > > [ovirt-3.5-epel] > name=Extra Packages for Enterprise Linux 6 - $basearch > #baseurl=http://download.fedoraproject.org/pub/epel/6/$basearch > mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-6&arch=$basearch > failovermethod=priority > enabled=1 > includepkgs=epel-release,python-uinput,puppet,python-lockfile,python-cpopen,python-ordereddict,python-pthreading,python-inotify,python-argparse,novnc,python-ply,python-kitchen,python-daemon,python-websockify,livecd-tools,spice-html5,mom,python-IPy,python-ioprocess,ioprocess,rubygem-rgen > gpgcheck=1 > gpgkey=https://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-6 > > > So why can engine depend on epel and vdsm can not?
engine and vdsm both can, and do, depend on epel. However, RHEV cannot. Taking an epel package has a price of needing to ship it in http://ftp.redhat.com/pub/redhat/rhev-m/3.x/SRPMS/ (see python-inotify there, as a vdsm dependency). In case of simplejson for el7, it simply does not worth it. _______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel