From: Robert Yang <liezhi.yang@windriver.com>
To: Li Zhou <li.zhou@windriver.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] opkg-utils: Change alternatives lib path from /usr/lib/opkg to /var/lib/opkg
Date: Thu, 11 Jun 2015 15:16:15 +0800 [thread overview]
Message-ID: <557935BF.70602@windriver.com> (raw)
In-Reply-To: <1432625185-12163-1-git-send-email-li.zhou@windriver.com>
Ping.
// Robert
On 05/26/2015 03:26 PM, Li Zhou wrote:
> When update-alternatives is moved from opkg to opkg-utils, a line in
> the file is changed
> from <ad="$OPKG_OFFLINE_ROOT@opkglibdir@/opkg/alternatives">
> to <ad="$OPKG_OFFLINE_ROOT/usr/lib/opkg/alternatives">.
> But opkglibdir doesn't equal to "/usr/lib" here, but equal to "/var/lib"
> in oe-core build by configuring --with-opkglibdir.
> opkg-utils can't get the var value in opkg, so here define OPKGLIBDIR to
> set the path.
>
> Signed-off-by: Li Zhou <li.zhou@windriver.com>
> ---
> meta/recipes-devtools/opkg-utils/opkg-utils_git.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> index 2800a5d..9c1c995 100644
> --- a/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> +++ b/meta/recipes-devtools/opkg-utils/opkg-utils_git.bb
> @@ -22,8 +22,11 @@ PYTHONRDEPS_class-native = ""
> PACKAGECONFIG = "python"
> PACKAGECONFIG[python] = ",,,${PYTHONRDEPS}"
>
> +OPKGLIBDIR ?= "/var/lib"
> +
> do_install() {
> oe_runmake PREFIX=${prefix} DESTDIR=${D} install
> + sed -i s:/usr/lib/opkg:${OPKGLIBDIR}/opkg: ${D}${bindir}/update-alternatives
> }
>
> PACKAGES =+ "update-alternatives-opkg"
>
next prev parent reply other threads:[~2015-06-11 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 7:26 [PATCH v3] opkg-utils: Change alternatives lib path from /usr/lib/opkg to /var/lib/opkg Li Zhou
2015-06-11 7:16 ` Robert Yang [this message]
2015-06-26 8:03 ` Rongqing Li
2015-07-10 2:22 ` Rongqing Li
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=557935BF.70602@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=li.zhou@windriver.com \
--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