Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	 openembedded-devel <openembedded-devel@lists.openembedded.org>,
	 Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [OE-core] [meta-openembedded][RFC] meta-multimedia layer
Date: Tue, 07 Feb 2012 15:03:44 -0800	[thread overview]
Message-ID: <4F31ADD0.9050206@linux.intel.com> (raw)
In-Reply-To: <20120207224904.GC13125@sakrah.homelinux.org>

On 02/07/2012 02:49 PM, Khem Raj wrote:
> On (07/02/12 12:08), Koen Kooi wrote:
>> Hi,
>>
>> During FOSDEM Paul Eggleton and I discussed moving a few multimedia recipes (libav, xbmc, faac, faad, etc) out of meta-oe into a new meta-multimedia layer hosted in the meta-openembedded git repo. This would allow e.g. meta-baryon to drop a number of recipes while avoiding the need to drag in the complete meta-oe layer.
>>
>> Thoughts?
>
> yes idea is fine. Will it then host all multimedia related stuff ? or
> just whats in meta-oe is being moved.
>
This is a good idea, we should get a good proposal so it's clear what's 
moving where and how.  Currently this should start with meta-oe and we 
can then evaluate if anything in oe-core should move there.

This is similar to the starting point we have with gnome, but we needed 
to keep some of that in core.

Thanks for the effort.

Sau!


> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



      reply	other threads:[~2012-02-07 23:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <29270F77-234D-4561-974D-C8E266898FA3@beagleboard.org>
     [not found] ` <4F314FEC.6090108@linux.intel.com>
2012-02-07 16:30   ` [OE-core] [meta-openembedded][RFC] meta-multimedia layer Koen Kooi
2012-02-07 22:49 ` Khem Raj
2012-02-07 23:03   ` Saul Wold [this message]

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=4F31ADD0.9050206@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.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