From: Joaquim Duran <joaquinduran@adtelecom.es>
To: Using the OpenEmbedded metadata to build Linux Distributions
<openembedded-devel@lists.openembedded.org>
Subject: Re: List of dependent packages
Date: Tue, 26 Sep 2006 17:01:56 +0100 [thread overview]
Message-ID: <45194EF4.3000208@adtelecom.es> (raw)
In-Reply-To: <74d0deb30609260757w5b4c2236nab1a8eafe527584e@mail.gmail.com>
Thanks.
Joaquim Duran
En/na pHilipp Zabel ha escrit:
> On 9/26/06, Joaquim Duran <joaquinduran@adtelecom.es> wrote:
>> Hello,
>>
>> Thanks for your answer. This is closer that I was looking for.
>>
>> I've tested both options (--dry-run) and (--graphviz).
>>
>> Using the first one with bootstrap image, the following output has been
>> shown (it shown that several packages should be used and I should choose
>> one):
>>
>> OE Build Configuration:
>> BB_VERSION = "1.6.1"
>> OE_REVISION = "57f56983ed32783fae7cfa0440e1f3a7cfc2280c"
>> TARGET_ARCH = "arm"
>> TARGET_OS = "linux"
>> MACHINE = "colibri"
>> DISTRO = "colibrioe"
>> DISTRO_VERSION = "1.0"
>> TARGET_FPU = ""
>>
>> NOTE: multiple providers are available (task-bootstrap-unionroot,
>> task-bootstrap);
>> NOTE: consider defining PREFERRED_PROVIDER_task-bootstrap
>> NOTE: package bootstrap-image-1.0: started
>> NOTE: package bootstrap-image-1.0: completed
>> NOTE: build 200609261620: completed
>
> I wonder if this NOTE should only be shown if there is no provider foo providing
> foo itself. If there is, PREFERRED_PROVIDER_foo ?= "foo" would then have
> to be set internally.
> It looks like now, every time somebody decides to provide an alternative to
> some existing package, everybody has to add PREFERRED_PROVIDER
> entries for this or live with the NOTEs.
>
>> The simple question is: how can I define
>> PREFERRED_PROVIDER_task-bootstrap line the local.conf file?
>
> PREFERRED_PROVIDER_task-bootstrap = "task-bootstrap"
>
> regards
> Philipp
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2006-09-26 15:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 11:22 List of dependent packages Joaquim Duran
2006-09-26 10:58 ` Christopher Lang
2006-09-26 12:36 ` Joaquim Duran
2006-09-26 12:01 ` Paul Sokolovsky
2006-09-26 13:47 ` Richard Purdie
2006-09-26 15:35 ` Joaquim Duran
2006-09-26 14:57 ` pHilipp Zabel
2006-09-26 15:26 ` Richard Purdie
2006-09-26 16:01 ` Joaquim Duran [this message]
2006-09-27 7:36 ` Joaquim Duran
2006-09-27 13:45 ` Ray Lehtiniemi
2006-09-27 13:53 ` Ray Lehtiniemi
2006-09-27 19:17 ` Paul Sokolovsky
2006-09-28 7:46 ` Joaquim Duran
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=45194EF4.3000208@adtelecom.es \
--to=joaquinduran@adtelecom.es \
--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