From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Avoiding registration as shlib provider
Date: Mon, 17 Mar 2014 10:22:39 +0100 [thread overview]
Message-ID: <20140317092239.GF3725@jama> (raw)
In-Reply-To: <5326BAC9.40201@pseudoterminal.org>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Mon, Mar 17, 2014 at 10:05:13AM +0100, Carlos Rafael Giani wrote:
> Hello,
>
> I have noticed the problem with GStreamer in current master: the many
> "xyz was registered as shlib provider" warnings.
> Actually, it makes no sense to register the plugins, since they are,
> well, plugins. No other package must have a hard dependency on any of
> them. So, it would make sense to disable registration for the plugins.
> Is this possible?
Yes it makes sense and it's possible by listing them in PRIVATE_LIBS
(PRIVATE_LIBS_${PN}-foo)
If you dont want to list them one-by-one than you'll have to wait for
http://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/shlib-providers&id=6bbe2582ecf4a6a8fb667e06b3a7bcbf917597a2
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-03-17 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 9:05 Avoiding registration as shlib provider Carlos Rafael Giani
2014-03-17 9:22 ` Martin Jansa [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=20140317092239.GF3725@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@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