Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Li Zhou <li.zhou@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] opkg-utils: Change alternatives lib path from /usr/lib/opkg to /var/lib/opkg
Date: Sat, 11 Jul 2015 23:39:32 +0100	[thread overview]
Message-ID: <1436654372.3310.28.camel@linuxfoundation.org> (raw)
In-Reply-To: <1432085475-24806-1-git-send-email-li.zhou@windriver.com>

On Wed, 2015-05-20 at 09:31 +0800, 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(+)

https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/387/steps/BuildImages_3/logs/stdio

Seems related to this :/

Cheers,

Richard



  parent reply	other threads:[~2015-07-11 22:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20  1:31 [PATCH] opkg-utils: Change alternatives lib path from /usr/lib/opkg to /var/lib/opkg Li Zhou
2015-05-20  6:07 ` Martin Jansa
2015-05-21 10:00   ` Zhou, Li
2015-07-11 22:39 ` Richard Purdie [this message]
2015-07-31  2:55   ` Rongqing Li
2015-07-31  3:20     ` ChenQi
2015-07-31  3:20       ` Rongqing Li
  -- strict thread matches above, loose matches on Subject: below --
2015-05-13  9:41 Li Zhou
2015-05-13  9:57 ` Martin Jansa

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=1436654372.3310.28.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --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