From: Phil Blundell <pb@pbcl.net>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] GStreamer 1.0 recipes
Date: Thu, 06 Jun 2013 22:01:58 +0100 [thread overview]
Message-ID: <1370552518.4141.10.camel@pb-ThinkPad-R50e> (raw)
In-Reply-To: <51B0EEA9.1030903@linux.intel.com>
On Thu, 2013-06-06 at 13:18 -0700, Saul Wold wrote:
> But back to the orignal question, is the gstreamer 1.0 an upgrade path
> for 0.10 or a completely new gstreamer? Is there an upgrade path? If
> so, then the packaging needs to reflect that.
I think what you're really asking is "is gstreamer 1.0 ABI-compatible
with 0.10?" and the answer to that question is no. Binaries compiled
against 0.10 will need recompiling to use 1.0 so RPROVIDES would make no
sense, and the two libraries are parallel installable so RCONFLICTS is
not necessary either. In any case, using RPROVIDES/RCONFLICTS for
libraries is sometimes slightly tricky in the presence of the debian
autonamer, and is generally something that ought to be left to those
distros that care about it rather than trying to solve the problem in
oe-core.
But all this is largely orthogonal to the question of whether or not we
want to keep both versions in OE-Core. There does exist some precedent
for that: we have both gtk2 and gtk3, and we also have multiple versions
of (at least) linux, pseudo and gcc already.
p.
next prev parent reply other threads:[~2013-06-06 21:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 19:15 [PATCH 0/3] GStreamer 1.0 recipes Carlos Rafael Giani
2013-05-31 19:15 ` [PATCH 1/3] gstreamer: fixed -meta package rdepends Carlos Rafael Giani
2013-05-31 19:15 ` [PATCH 2/3] gstreamer: moved LIBV out of gst-plugins-package.inc file Carlos Rafael Giani
2013-05-31 19:15 ` [PATCH 3/3] gstreamer: added GStreamer 1.0 recipes Carlos Rafael Giani
2013-06-06 16:53 ` [PATCH 0/3] " Saul Wold
2013-06-06 17:17 ` Carlos Rafael Giani
2013-06-06 20:18 ` Saul Wold
2013-06-06 21:01 ` Phil Blundell [this message]
2013-06-06 21:05 ` Carlos Rafael Giani
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=1370552518.4141.10.camel@pb-ThinkPad-R50e \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--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