From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: update-alternatives setting problem in OE
Date: Thu, 23 Apr 2015 16:14:56 +0800 [thread overview]
Message-ID: <5538AA00.8060706@windriver.com> (raw)
Hi All,
In OE, we have three providers for update-alternatives, dpkg, opkg-utils
and chkconfig.
We default to use the following setting in default-providers.inc.
PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg-utils"
PREFERRED_PROVIDER_virtual/update-alternatives-native ?= "opkg-utils-native"
VIRTUAL-RUNTIME_update-alternatives ?= "update-alternatives-opkg"
The problem here is that *the above setting seems to be the only valid
setting in OE*.
If we change the provider, things don't build.
If we change the VIRTUAL-RUNTIME_update-alternatives setting, runtime
behaviours for 'update-alternatives' are not correct. Because there
three different update-alternatives use different databases.
I'm sending out this email to see if anyone ever encounters the same
problem.
I also checked the ref manual of Yocto, no related information or
warnings there.
Best Regards,
Chen Qi
reply other threads:[~2015-04-23 8:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5538AA00.8060706@windriver.com \
--to=qi.chen@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