From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-commits@lists.openembedded.org
Subject: Re: [oe-commits] Paul Barker : default-providers: Change update-alternatives provider to opkg-utils
Date: Tue, 21 Jan 2014 23:41:55 +0100 [thread overview]
Message-ID: <20140121224155.GJ4100@jama> (raw)
In-Reply-To: <20140119164038.2027F502E0@opal>
[-- Attachment #1: Type: text/plain, Size: 2789 bytes --]
On Sun, Jan 19, 2014 at 04:40:38PM +0000, git@git.openembedded.org wrote:
> Module: openembedded-core.git
> Branch: master
> Commit: 2f18289493f9c2c67ba343fb8e16743bf5dfee24
> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=2f18289493f9c2c67ba343fb8e16743bf5dfee24
>
> Author: Paul Barker <paul@paulbarker.me.uk>
> Date: Thu Jan 16 17:59:25 2014 +0000
>
> default-providers: Change update-alternatives provider to opkg-utils
>
> This allows dependencies to be added to the opkg recipe without causing circular
> dependency loops. As opkg-utils has minimal dependencies it is the best recipe
> to provide update-alternatives.
>
> This partially solves Yocto Project issue 4836. More work is still needed for a
> complete solution.
>
> Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> ---
>
> meta/conf/distro/include/default-providers.inc | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/meta/conf/distro/include/default-providers.inc b/meta/conf/distro/include/default-providers.inc
> index e2b0892..419ffcd 100644
> --- a/meta/conf/distro/include/default-providers.inc
> +++ b/meta/conf/distro/include/default-providers.inc
> @@ -10,15 +10,15 @@ PREFERRED_PROVIDER_virtual/libgl ?= "mesa"
> PREFERRED_PROVIDER_virtual/libgles1 ?= "mesa"
> PREFERRED_PROVIDER_virtual/libgles2 ?= "mesa"
> PREFERRED_PROVIDER_virtual/mesa ?= "mesa"
> -PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg"
> -PREFERRED_PROVIDER_virtual/update-alternatives-native ?= "opkg-native"
> +PREFERRED_PROVIDER_virtual/update-alternatives ?= "opkg-utils"
> +PREFERRED_PROVIDER_virtual/update-alternatives-native ?= "opkg-utils-native"
> PREFERRED_PROVIDER_virtual/libx11 ?= "libx11"
> PREFERRED_PROVIDER_xf86-video-intel ?= "xf86-video-intel"
>
> #
> # Default virtual runtime providers
> #
> -VIRTUAL-RUNTIME_update-alternatives ?= "update-alternatives-cworth"
> +VIRTUAL-RUNTIME_update-alternatives ?= "update-alternatives-opkg"
Can we add RREPLACES/RCONFLICTS/RPROVIDES combo to opkg-utils recipe to
fix upgrade-path on target?
* check_data_file_clashes: Package update-alternatives-opkg wants to
* install file /usr/bin/update-alternatives
But that file is already provided by package * update-alternatives-cworth
I'll send patch.
> VIRTUAL-RUNTIME_apm ?= "apm"
> VIRTUAL-RUNTIME_alsa-state ?= "alsa-state"
>
>
> _______________________________________________
> Openembedded-commits mailing list
> Openembedded-commits@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-commits
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
parent reply other threads:[~2014-01-21 22:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20140119164038.2027F502E0@opal>]
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=20140121224155.GJ4100@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox