From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: RFC: gstreamer 1.0 recipes
Date: Tue, 09 Apr 2013 11:50:16 +0200 [thread overview]
Message-ID: <5163E458.1080709@pseudoterminal.org> (raw)
In-Reply-To: <CAJTo0La+4zFbSu1s8mDQ=oWUEzasRgi9Ufg433qbB=8sbde1gw@mail.gmail.com>
On 2013-04-09 11:32, Burton, Ross wrote:
> On 9 April 2013 00:00, Carlos Rafael Giani <dv@pseudoterminal.org> wrote:
>> thinking about this whole issue I began to wonder: why is gstreamer in
>> oe-core and not in meta-multimedia?
>> wouldnt it be easier then to move liborc into meta-multimedia as well?
>> Or is gstreamer considered an essential component for many installations,
>> thus justifying its presence in oe-core?
> Yes, it's common enough, and I'd support moving liborc to oe-core in 1.5.
>
> There's always a grey area for oe-core verses meta-something, but
> there's no point in oe-core just consisting of gcc and libc.
>
> Ross
Okay, sounds good. But just liborc? Or yasm as well? yasm is crucial for
ffmpeg and libav.
Carlos
next prev parent reply other threads:[~2013-04-09 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 23:38 RFC: gstreamer 1.0 recipes Carlos Rafael Giani
2013-04-08 7:57 ` Koen Kooi
2013-04-08 9:35 ` Burton, Ross
2013-04-08 10:47 ` Koen Kooi
2013-04-08 11:09 ` Paul Eggleton
2013-04-08 11:14 ` Carlos Rafael Giani
2013-04-08 9:36 ` Carlos Rafael Giani
2013-04-15 1:21 ` Carlos Rafael Giani
2013-04-08 13:39 ` Otavio Salvador
2013-04-08 23:00 ` Carlos Rafael Giani
2013-04-09 9:32 ` Burton, Ross
2013-04-09 9:50 ` Carlos Rafael Giani [this message]
2013-04-09 10:02 ` Burton, Ross
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=5163E458.1080709@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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