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: Fri, 23 Mar 2012 11:46:42 +0000 [thread overview]
Message-ID: <1332503202.9740.391.camel@ted> (raw)
In-Reply-To: <CAGiJk9evph+E_CzqN9iOAqAD9ypkcDvV9xj2LrkD1O05Dv=CbA@mail.gmail.com>
On Fri, 2012-03-23 at 09:00 +0100, Samuel Stirtzel wrote:
> 2012/3/23 Andrea Adami <andrea.adami@gmail.com>:
> > On Thu, Mar 22, 2012 at 4:58 PM, Saul Wold <sgw@linux.intel.com> wrote:
> >> On 03/22/2012 02:41 AM, Samuel Stirtzel wrote:
> >>>
> >>> 2012/3/22 Koen Kooi<koen@dominion.thruhere.net>:
> >>>>
> >>>>
> >>>> Op 22 mrt. 2012, om 09:48 heeft Samuel Stirtzel het volgende geschreven:
> >>>>
> >>>>> 2012/3/21 Koen Kooi<koen@dominion.thruhere.net>:
> >>>>>>
> >>>>>>
> >>>>>> 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!
> >>>>>
> >>>>>
> >>>>> Otherwise it would require to maintain a redundant copy of giflib in
> >>>>> meta-kde.
> >>>>
> >>>>
> >>>> I don't think you get the concept of layers and keeping non-core stuff
> >>>> out of oe-core.
> >>>
> >>>
> >>> How can it be that libpng is core stuff and libgif is not?
> >>>
> >> libpng is in oe-core because it is used by other parts of oe-core (Sato,
> >> GTK+, Gthumb, Cups, ...). PNG is also more common that GIF because GIF had
> >> licensing issues in the past.
> >
> > All this seems to me unsatisfactory being that the above mentioned
> > 'parts of OE' should not even be in oe-core.
> > About the specific .gif, .png , etc. libs, those should be in a
> > meta-graphics layer or whatever you want to call it.
>
> There is a layer called meta-multimedia, would giflib, libpng and the
> others fit into it?
I think people are focusing on libpng a little too much here.
libpng turns out to be an order of magnitude more important than giflib
due to the fact that pretty much any graphical UI uses them at this
point. To remove libpng from OE-Core we'd have to remove the X11 stack
and pretty much anything graphical (core gnome, QT and probably sdl and
directfb). That is not what we're trying to achieve in the core and not
in the best interests of OE.
giflib on the other hand is used more on the fringes of the system,
clearly demonstrated that we have a solid graphic core and don't need
it.
You can't just say "its a multimedia format so it belongs in
meta-multimedia" as you have to consider what depends on it and how
important it is in the overall web of dependencies.
I realise this situation is messy. Its a hard problem.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-23 11: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
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 [this message]
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=1332503202.9740.391.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