* update-alternatives setting problem in OE
@ 2015-04-23 8:14 ChenQi
0 siblings, 0 replies; only message in thread
From: ChenQi @ 2015-04-23 8:14 UTC (permalink / raw)
To: openembedded-core
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-04-23 8:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-23 8:14 update-alternatives setting problem in OE ChenQi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox