Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: Saul Wold <sgw@linux.intel.com>,  "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: Request for moving Orc to OE-core
Date: Wed, 06 Nov 2013 19:27:54 +0100	[thread overview]
Message-ID: <527A8A2A.6040400@pseudoterminal.org> (raw)
In-Reply-To: <527A8217.8090605@linux.intel.com>

On 2013-11-06 18:53, Saul Wold wrote:
> On 11/06/2013 07:47 AM, Burton, Ross wrote:
>> On 6 November 2013 14:47, Carlos Rafael Giani <dv@pseudoterminal.org> 
>> wrote:
>>> As preparation for upgrading the gstreamer1.0 recipes to 1.2 , I would
>>> propose to move Orc into OE-core.
>>> Without Orc, key elements of GStreamer (audioconvert, audioresample,
>>> videoconvert, videoscale ..) are much slower.
>>> Currently Orc is in meta-oe . Its recipe uses the most recent version
>>> (0.4.18), which is the minimum Orc version that works with GStreamer 
>>> 1.2. If
>>> Orc is in oe-core, it can be added to the
>>> gstreamer1.0-plugins-base/good/bad/ugly recipes' default PACKAGECONFIG
>>> lists.
>>
>> I agree with this, and have wanted to do this for a while now.
>>
>
> Carlos,
>
> please make it so and thanks for working on the gstreamer update.
>
> Sau!
>
>> Ross
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>

Moving Orc involves moving a file from one repo to the other. How is 
this usually handled?
By submitting one patch to OE-core (adding Orc) and one to meta-oe 
(removing Orc) at the same time?
Or is there a better way?


  reply	other threads:[~2013-11-06 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 14:47 Request for moving Orc to OE-core Carlos Rafael Giani
2013-11-06 15:47 ` Burton, Ross
2013-11-06 17:53   ` Saul Wold
2013-11-06 18:27     ` Carlos Rafael Giani [this message]
2013-11-06 18:32       ` Saul Wold

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=527A8A2A.6040400@pseudoterminal.org \
    --to=dv@pseudoterminal.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    --cc=sgw@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