From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 5/5] libav: Change the PACKAGES_DYNAMIC expression to be more restrict
Date: Wed, 10 Oct 2012 10:38:42 +0200 [thread overview]
Message-ID: <50753412.80107@linaro.org> (raw)
In-Reply-To: <1349554710-6693-5-git-send-email-otavio@ossystems.com.br>
W dniu 06.10.2012 22:18, Otavio Salvador pisze:
> Using 'lib*' we end having problem with every other package that
> generate libraries dynamically thus we changed it to match the library
> prefixes.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
> meta-oe/recipes-multimedia/libav/libav.inc | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta-oe/recipes-multimedia/libav/libav.inc b/meta-oe/recipes-multimedia/libav/libav.inc
> index aa170c5..4a1716f 100644
> --- a/meta-oe/recipes-multimedia/libav/libav.inc
> +++ b/meta-oe/recipes-multimedia/libav/libav.inc
> @@ -119,4 +119,4 @@ python populate_packages_prepend() {
> allow_links=True)
> }
>
> -PACKAGES_DYNAMIC = "lib*"
> +PACKAGES_DYNAMIC = "lib(av(codec|device|filter|format|util)|postproc)*"
Can it get merged? Or should we keep copy of libav in external layers?
prev parent reply other threads:[~2012-10-10 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 20:18 [meta-oe][PATCH 1/5] owfs: Update to 2.8p20 version Otavio Salvador
2012-10-06 20:18 ` [meta-oe][PATCH 2/5] yajl: Update to 2.0.4 version Otavio Salvador
2012-10-06 20:18 ` [meta-oe][PATCH 3/5] libpostproc: Add git version Otavio Salvador
2012-10-06 20:18 ` [meta-oe][PATCH 4/5] libav: Update git version to 2012-10-04 snapshot Otavio Salvador
2012-10-06 20:18 ` [meta-oe][PATCH 5/5] libav: Change the PACKAGES_DYNAMIC expression to be more restrict Otavio Salvador
2012-10-10 8:38 ` Marcin Juszkiewicz [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=50753412.80107@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--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