From: Rongqing Li <rongqing.li@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH][meta-networking] mime-construct: Perform more mangling for perl path
Date: Mon, 4 Jan 2016 16:53:39 +0800 [thread overview]
Message-ID: <568A3313.7050802@windriver.com> (raw)
In-Reply-To: <1451870041-5001-1-git-send-email-rongqing.li@windriver.com>
sorry, please drop this patch
-Roy
On 2016年01月04日 09:14, rongqing.li@windriver.com wrote:
> From: Roy Li <rongqing.li@windriver.com>
>
> native perl is in /usr/bin/mime-construct, introduce the below
> QA warning, it should be replaced:
>
> WARNING: QA Issue: /usr/bin/mime-construct_mime-construct contained in package mime-construct requires
> tmp/sysroots/x86_64-linux/usr/bin/perl-native/perl, but no providers found in its RDEPENDS [file-rdeps]
>
> Signed-off-by: Roy Li <rongqing.li@windriver.com>
> ---
> .../recipes-extended/mime-construct/mime-construct_1.11.bb | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/meta-networking/recipes-extended/mime-construct/mime-construct_1.11.bb b/meta-networking/recipes-extended/mime-construct/mime-construct_1.11.bb
> index 6db4fdf..61bcd13 100644
> --- a/meta-networking/recipes-extended/mime-construct/mime-construct_1.11.bb
> +++ b/meta-networking/recipes-extended/mime-construct/mime-construct_1.11.bb
> @@ -20,3 +20,9 @@ inherit cpan
> RDEPENDS_${PN} = "msmtp perl perl-module-mime-base64 perl-module-mime-quotedprint \
> libproc-waitstat-perl libmime-types-perl perl-module-filehandle perl-module-posix \
> "
> +
> +do_install_append() {
> + #change the interpreter in file
> + sed -i -e "s|${STAGING_BINDIR_NATIVE}/perl-native/perl -w|${bindir}/env perl|g" \
> + ${D}/${bindir}/mime-construct
> +}
>
--
Best Reagrds,
Roy | RongQing Li
prev parent reply other threads:[~2016-01-04 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 1:14 [PATCH][meta-networking] mime-construct: Perform more mangling for perl path rongqing.li
2016-01-04 8:53 ` Rongqing Li [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=568A3313.7050802@windriver.com \
--to=rongqing.li@windriver.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 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.