From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image
Date: Wed, 26 Nov 2008 19:33:29 +0100 [thread overview]
Message-ID: <ggk4pp$c9e$1@ger.gmane.org> (raw)
In-Reply-To: <20081126182400.GA27631@denix.org>
On 26-11-08 19:24, Denys Dmytriyenko wrote:
> On Wed, Nov 26, 2008 at 09:12:34PM +0300, Sergey Lapin wrote:
>> I just need to mention we have same kind of problems with mplayer vs
>> mplayer-maemo recipe,
>> when you try to put e.g. mencoder into IMAGE_INSTALL, mplayer-maemo
>> recipe is used instead of mplayer one.
>> Also, which is weird, I was able to reproduce this lots of times on
>> one my setup even with build from scratch,
>> and was unable to do so with my another setup.
>
> Sorry for my naive question, but why can't it be specified with
>
> PREFERRED_PROVIDER_mplayer = "mplayer"
That works at buildtime, opkg doesn't know about preferred_provider.
regards,
Koen
next prev parent reply other threads:[~2008-11-26 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 14:51 preferred-provider at the image level a.k.a why is all this fso stuff in my non-fso image Koen Kooi
2008-11-26 16:55 ` Michael 'Mickey' Lauer
2008-11-26 17:28 ` Koen Kooi
2008-11-26 17:40 ` Phil Blundell
2008-11-26 17:49 ` Koen Kooi
2008-11-26 18:03 ` Phil Blundell
2008-11-26 18:40 ` Koen Kooi
2008-11-26 19:00 ` Phil Blundell
2008-11-26 20:09 ` Koen Kooi
2008-11-26 21:27 ` Phil Blundell
2008-11-27 7:34 ` Koen Kooi
2008-11-26 18:12 ` Sergey Lapin
2008-11-26 18:24 ` Denys Dmytriyenko
2008-11-26 18:33 ` Koen Kooi [this message]
2008-11-26 18:45 ` Denys Dmytriyenko
2008-11-26 18:35 ` Phil Blundell
2008-11-28 9:40 ` Koen Kooi
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='ggk4pp$c9e$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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