[oe] [oe-commits] Koen Kooi : efl: bump SRCREV for comp fixes

Martin Jansa martin.jansa at gmail.com
Tue Feb 9 10:50:23 UTC 2010


On Sun, Feb 7, 2010 at 11:24 AM, git version control
<git at git.openembedded.org> wrote:
> Module: openembedded.git
> Branch: org.openembedded.dev
> Commit: 17367574b9a7e5030e8ec5e69d10119d647f2170
> URL:    http://gitweb.openembedded.net/?p=openembedded.git&a=commit;h=17367574b9a7e5030e8ec5e69d10119d647f2170
>
> Author: Koen Kooi <koen at openembedded.org>
> Date:   Fri Feb  5 20:16:18 2010 +0100
>
> efl: bump SRCREV for comp fixes
> -EFL_SRCREV ?= "45765"
> +EFL_SRCREV ?= "45902"

With this revision epsilon started to fail (python-epsilon was failing
before too).
http://tinderbox.openembedded.net/packages/epsilon/
http://tinderbox.openembedded.net/packages/python-epsilon/

I asked upstream devs on #edevel for simple fix and they said, that
epsilon is so unsupported that they would rather move it from OLD/ to
BROKEN/.

What's right way to handle that in OE?
Is it worth maintaining epsilon alive in oe.dev and asking upstream to
include patches for epsilon or can we move epsilon + apps depending on
it to obsoleted?

We cannot bump ecore, because of epsilon which is pity. If we move
epsilon to recipes/obsoleted then there is few apps still using that:
e17/exhibit_svn.bb:DEPENDS = "evas ecore epsilon edje eet etk efreet"
efl1/epdf/fix-plugin-path-check.patch:    requirements="$requirements
epsilon imlib2"
efl1/epsilon_svn.bb:FILES_${PN}-thumbd = "${bindir}/epsilon
${bindir}/epsilon_thumbd"
efl1/esmart_svn.bb:DEPENDS = "evas ecore edje imlib2 epsilon libtool"
efl1/ewl_svn.bb:DEPENDS = "evas ecore edje emotion efreet epsilon"
omview/omview_svn.bb:DEPENDS += " evas ewl epsilon"
python/python-epsilon_svn.bb:DEPENDS += "epsilon python-ecore"
tasks/task-efl.bb:  epsilon \
tasks/task-openmoko-feed.bb:  eet evas ecore embryo epsilon edje
efreet emotion epdf \
tasks/task-python-efl-examples.bb:  python-epsilon-examples \
tasks/task-python-efl.bb:  python-epsilon \

Regards,




More information about the Openembedded-devel mailing list