From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [RFC 1/2] gstreamer: sync packaging with OE .dev
Date: Fri, 16 Sep 2011 11:09:49 +0100 [thread overview]
Message-ID: <1316167797.25993.70.camel@ted> (raw)
In-Reply-To: <1316161201-769-1-git-send-email-koen@dominion.thruhere.net>
On Fri, 2011-09-16 at 10:20 +0200, Koen Kooi wrote:
> some text here
It took all my restraint to not just reply with:
"""
NAK
<insert reason for NAK here, I can't be bothered to type it>
"""
We've been around in a few circles with this. The problem is that if we
apply this patch we have no clue which gst-plugin from the good, the bad
and the ugly provides something you're after to include in an image.
This results in bitbake being pretty clueless about whether a given
build will succeed or not. In general I'm not a fan of having
non-deterministic builds as they tend to annoy users.
If this position isn't acceptable then we'll probably have to move to a
situation where we list which plugins each of the packages builds and
drop the dyanmic provides. That is a maintenance pain and I don't take
that step lightly but I don't see any other options. I'm open to
suggestions though.
Cheers,
Richard
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> .../gstreamer/gst-plugins-package.inc | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-multimedia/gstreamer/gst-plugins-package.inc b/meta/recipes-multimedia/gstreamer/gst-plugins-package.inc
> index 796df14..dae9416 100644
> --- a/meta/recipes-multimedia/gstreamer/gst-plugins-package.inc
> +++ b/meta/recipes-multimedia/gstreamer/gst-plugins-package.inc
> @@ -6,8 +6,8 @@ python populate_packages_prepend () {
> glibdir = bb.data.expand('${libdir}', d)
>
> do_split_packages(d, glibdir, '^lib(.*)\.so\.*', 'lib%s', 'gstreamer %s library', extra_depends='', allow_links=True)
> - do_split_packages(d, gst_libdir, 'libgst(.*)\.so$', bb.data.expand('${PN}-%s', d), 'GStreamer plugin for %s', postinst=postinst, extra_depends=bb.data.expand('${PN}',d))
> - do_split_packages(d, gst_libdir, 'libgst(.*)\.l?a$', bb.data.expand('${PN}-%s-dev', d), 'GStreamer plugin for %s (development files)', extra_depends=bb.data.expand('${PN}-dev',d))
> + do_split_packages(d, gst_libdir, '^libgst(.*)\.so$', 'gst-plugin-%s', 'GStreamer plugin for %s', postinst=postinst, extra_depends='')
> + do_split_packages(d, gst_libdir, '^libgst(.*)\.l?a$', 'gst-plugin-%s-dev', 'GStreamer plugin for %s (development files)', extra_depends='')
>
> pn = bb.data.getVar('PN', d, 1)
> metapkg = pn + '-meta'
next prev parent reply other threads:[~2011-09-16 10:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 8:20 [RFC 1/2] gstreamer: sync packaging with OE .dev Koen Kooi
2011-09-16 8:20 ` [RFC 2/2] gst-meta-base: adjust plugin names after gstreamer packaging changes Koen Kooi
2011-09-16 10:09 ` Richard Purdie [this message]
2011-09-16 10:19 ` [RFC 1/2] gstreamer: sync packaging with OE .dev Martin Jansa
2011-09-16 11:00 ` Richard Purdie
2011-09-16 11:06 ` Phil Blundell
2011-09-16 13:38 ` Richard Purdie
2011-09-22 11:32 ` Koen Kooi
2011-09-26 18:38 ` Richard Purdie
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=1316167797.25993.70.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox