From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Carlos Rafael Giani <dv@pseudoterminal.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Questions about Orc and GStreamer
Date: Mon, 30 Sep 2013 09:26:38 +0100 [thread overview]
Message-ID: <2097746.hRm7Rg6kXR@helios> (raw)
In-Reply-To: <52493149.3030403@pseudoterminal.org>
Hi Carlos,
On Monday 30 September 2013 10:07:37 Carlos Rafael Giani wrote:
> Yes, thats Orc. It is part of meta-oe , but really should be in OE-core.
> I think there was a discussion about this in OE-core months ago, and I
> didn't see an opinion against it.
> Can the GStreamer upgrade be included in the dora branch after release?
> I remember seeing package upgrades in the dylan happening after its
> release. In other words, package upgrades aren't just restricted to the
> master branch, correct?
The answer is we generally don't do upgrades on stable branches unless there
is a very good reason (for example, a security bug where it is more practical
to just upgrade to a new version for the recipe instead of trying to backport
patches to the existing version).
Specifically regarding gstreamer 1.2, I'm not too keen on the idea of upgrading
it in a stable branch - I've been told that there have been backwards-
incompatible changes since 1.0; if that is the case it wouldn't really be
appropriate. FWIW, the option as always is open to add the new version as a
separate layer on top of dylan.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
prev parent reply other threads:[~2013-09-30 8:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 21:49 Questions about Orc and GStreamer Carlos Rafael Giani
2013-09-30 8:02 ` Iorga, Cristian
2013-09-30 8:07 ` Carlos Rafael Giani
2013-09-30 8:26 ` Paul Eggleton [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=2097746.hRm7Rg6kXR@helios \
--to=paul.eggleton@linux.intel.com \
--cc=dv@pseudoterminal.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.