From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] giflib: Move to OE-Core
Date: Thu, 22 Mar 2012 07:59:40 +0100 [thread overview]
Message-ID: <20120322065940.GC4010@jama.jama.net> (raw)
In-Reply-To: <CAMKF1sqvv+x2tf4eT7Y7yf9MYLh4cf+o__kGoL+hup-xnb9q+A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
On Wed, Mar 21, 2012 at 09:47:43PM -0700, Khem Raj wrote:
> On Wed, Mar 21, 2012 at 1:27 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> 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!
And then again and again!
> >
> > 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.
> >
>
> I think this library could belong to OE-Core since its a library for GIF images
> its currently used by EFL libs. Putting it in OE-Core would be a better thing
> IMO since it seems common library
FWIW: meta-efl depends on more stuff from meta-oe so moving giflib won't
remove meta-oe dependency from meta-efl.
Cheers,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2012-03-22 7:08 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
2012-03-22 4:47 ` Khem Raj
2012-03-22 6:59 ` Martin Jansa [this message]
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=20120322065940.GC4010@jama.jama.net \
--to=martin.jansa@gmail.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