From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] giflib: Move to OE-Core
Date: Wed, 21 Mar 2012 20:27:07 +0000 [thread overview]
Message-ID: <1332361627.9740.180.camel@ted> (raw)
In-Reply-To: <FC6FAFAF-2C6E-4EF7-8AD9-D2C30D2114DD@dominion.thruhere.net>
On Wed, 2012-03-21 at 21:14 +0100, Koen Kooi wrote:
> Op 21 mrt. 2012, om 20:42 heeft Saul Wold het volgende geschreven:
>
> > On 03/21/2012 07:25 AM, Samuel Stirtzel wrote:
> >> * This move will allow the testing of meta-kde for users without meta-openembedded.
> >>
> > So what other layers are using giflib?
> >
> > Your suggesting that we need to have it in oe-core so people don't need to add the meta-openembedded layer when using meta-kde?
> >
> > I am just trying to get more data before making a decision.
>
> Let's put everything in oe-core!
Let's try and be constructive ;-).
I think to make a good decision about this we need to understand which
layers use giflib.
Is this really the only component from meta-oe that meta-kde needs? If
it is, I think the request is certainly worth thinking about as we do
want to try and minimise and untangle the dependency spider web if we
can.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-21 20:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 14:25 [PATCH] giflib: Move to OE-Core Samuel Stirtzel
2012-03-21 19:42 ` Saul Wold
2012-03-21 20:14 ` Koen Kooi
2012-03-21 20:27 ` Richard Purdie [this message]
2012-03-22 3:22 ` Robert Yang
2012-03-22 3:36 ` Denys Dmytriyenko
2012-03-22 6:46 ` Robert Yang
2012-03-22 4:47 ` Khem Raj
2012-03-22 6:59 ` Martin Jansa
2012-03-22 8:48 ` Samuel Stirtzel
2012-03-22 8:51 ` Koen Kooi
2012-03-22 9:41 ` Samuel Stirtzel
2012-03-22 15:58 ` Saul Wold
2012-03-22 23:27 ` Andrea Adami
2012-03-22 23:58 ` Denys Dmytriyenko
2012-03-23 8:00 ` Samuel Stirtzel
2012-03-23 11:46 ` Richard Purdie
2012-03-27 22:01 ` Khem Raj
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=1332361627.9740.180.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox