From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: etk is in obsolete but there are recipes which depend on it
Date: Thu, 19 Aug 2010 06:57:39 +0200 [thread overview]
Message-ID: <20100819045739.GH11569@jama> (raw)
In-Reply-To: <AANLkTin0-uaqPsLGigEpmHyOPxyDV3SW_6qS0m2nPvfc@mail.gmail.com>
On Wed, Aug 18, 2010 at 11:09:35PM +0200, Frans Meulenbroeks wrote:
> 2010/8/18 Khem Raj <raj.khem@gmail.com>:
> > Hi
> >
> > This commit below moved etk to obsolete
> >
> > commit bd75858d8e523dfbed244bf4046b5ce01eeee690
> > Author: Martin Jansa <Martin.Jansa@gmail.com>
> > Date: Fri Mar 19 18:14:59 2010 +0100
> >
> > efl: move epsilon/etk to obsolete, because they're not supported
> > with newer ecore anymore
> >
> > Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> >
> >
> > However there are recipes which still depend on this
> >
> > e17/e17edje-player_svn.bb
> > e17/edje-editor_svn.bb
> > comic-reader/comic-reader_svn.bb
> > e17/exhibit_svn.bb
> > efl1/eflpp_svn.bb
> > efl1/evolve_svn.bb
> > openmoko-projects/om-locations_git.bb
> > openmoko-projects/diversity-radar_svn.bb
> > openmoko-projects/assassin_svn.bb
> >
> > should they also find their way into obsolete ? or is there a new
> > replacement package they should depend on
I agree that moving them to obsolete after double checking that they
really depends on etk is good plan, also proposed a while back:
http://www.mail-archive.com/openembedded-devel@lists.openembedded.org/msg04242.html
I have EFL SRCREV upgrade in my queue (waiting for remaining alpha
releases like elementary)
http://gitorious.org/~jama/angstrom/jama-shr-experimental/
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-08-19 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 20:52 etk is in obsolete but there are recipes which depend on it Khem Raj
2010-08-18 21:09 ` Frans Meulenbroeks
2010-08-19 4:57 ` Martin Jansa [this message]
2010-08-19 6:43 ` Stefan Schmidt
2010-08-19 9:04 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100819045739.GH11569@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.