All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leon Woestenberg" <leon.woestenberg@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Stop on multiple providers but none explicitly specified
Date: Mon, 19 May 2008 00:48:29 +0200	[thread overview]
Message-ID: <c384c5ea0805181548o7efe0dc5h5c79b0dccc0d4300@mail.gmail.com> (raw)
In-Reply-To: <1211061548.5272.21.camel@dax.rpnet.com>

Richard,

On Sat, May 17, 2008 at 11:59 PM, Richard Purdie <rpurdie@rpsys.net> wrote:
> On Fri, 2008-05-16 at 23:44 +0200, Leon Woestenberg wrote:
>> PROVIDER_PREFERENCE seems a bridge too far for me, but hey, any
>> solution that solves it is better then the current situation.
>
> Its the only solution I can see which addresses the problem but it does
> further complicate the providers logic in bitbake which is already
> painful and in need of rewriting :/. Other solutions welcome...
>
The idea of bailing out when no preferred provider has been set is
(1) simple
(2) deterministic
(3) simple

Why make it harder then necessary? The stuff is complicated enough as
it is, especially for new ppl.

Regards,
-- 
Leon



  reply	other threads:[~2008-05-18 22:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 21:36 [RFC] Stop on multiple providers but none explicitly specified Leon Woestenberg
2008-05-15 16:42 ` Richard Purdie
2008-05-15 18:38   ` Tom Rini
2008-05-15 18:51   ` Leon Woestenberg
2008-05-15 20:11     ` Tom Rini
2008-05-15 20:50       ` Leon Woestenberg
2008-05-15 22:06         ` Tom Rini
2008-05-15 22:25         ` Koen Kooi
2008-05-15 21:45     ` Richard Purdie
2008-05-16 21:44       ` Leon Woestenberg
2008-05-17 21:59         ` Richard Purdie
2008-05-18 22:48           ` Leon Woestenberg [this message]
2008-05-19  8:38             ` Richard Purdie

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=c384c5ea0805181548o7efe0dc5h5c79b0dccc0d4300@mail.gmail.com \
    --to=leon.woestenberg@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.