Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] giflib: Move to OE-Core
Date: Thu, 22 Mar 2012 14:46:28 +0800	[thread overview]
Message-ID: <4F6ACAC4.1060501@windriver.com> (raw)
In-Reply-To: <20120322033624.GI6857@denix.org>



On 03/22/2012 11:36 AM, Denys Dmytriyenko wrote:
> On Thu, Mar 22, 2012 at 11:22:42AM +0800, Robert Yang wrote:
>>
>>
>> On 03/22/2012 04:27 AM, Richard Purdie wrote:
>>> 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
>>
>> Yes, as far as we know, this is the only component from meta-oe that
>> meta-kde needs.
>
> Are you talking about kdelibs/kdebase or the entire KDE world? Building any of

I just meant the kdebase, a base kde desktop, the kde-workspace which
can start the kde by command "startkde".

// Robert

> the standard KDE apps (kdenetwork, kdemultimedia, etc.) will bring additional
> dependencies...
>



  reply	other threads:[~2012-03-22  6:55 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
2012-03-22  3:22       ` Robert Yang
2012-03-22  3:36         ` Denys Dmytriyenko
2012-03-22  6:46           ` Robert Yang [this message]
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=4F6ACAC4.1060501@windriver.com \
    --to=liezhi.yang@windriver.com \
    --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