All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Brad Litterell <bradl@taser.com>
Cc: yocto@yoctoproject.org
Subject: Re: What are _virtual providers? and other Suffixes?
Date: Wed, 21 Aug 2013 15:26:08 +0100	[thread overview]
Message-ID: <11108180.KlZSWrBJZD@helios> (raw)
In-Reply-To: <2C678312-32B2-4184-9839-73D77D06525A@taser.com>

Hi Brad,

On Tuesday 20 August 2013 23:42:36 Brad Litterell wrote:
> Thanks - that makes it clearer.  But now I have one other question to ask:
> 
> if  virtual/xyz is added to overrides when the item is dealt with, then in
> that case P_P_virtual/xyz_am335 has two overrides hanging off of the base
> variable PREFERRED_PROVIDER.
> 
> You also said earlier that the latest override applies, so is there some
> rule for multiple conditionals on a variable?

Yes, effectively all must be in OVERRIDES for the assignment statement to take 
effect.
 
> E.g. What happens in a case like the following?
> 
> OVERRIDES="foo1:bar2:car3"
> 
> VARIABLE_foo1_bar2 = "both"
> VARIABLE_car3 = "last one"
> 
> what does VARIABLE wind up?  The first is "more specific" in that it matches
> two values in overrides, whereas car is last, but less specific.

I would have thought that the value would have been "last one" however 
experimentation shows that "both" is what you actually get. I'm not exactly 
sure why. In practice I don't think we hit this kind of situation too often 
though, i.e. a mix of double and single overrides where the single override 
needs to take precedence.
 
Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-08-21 14:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 22:51 What are _virtual providers? and other Suffixes? Brad Litterell
2013-08-20 22:27 ` Paul Eggleton
2013-08-20 23:16   ` Brad Litterell
2013-08-20 23:33     ` Paul Eggleton
2013-08-20 23:42       ` Brad Litterell
2013-08-21 14:26         ` Paul Eggleton [this message]
2013-08-21 16:27           ` Brad Litterell

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=11108180.KlZSWrBJZD@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=bradl@taser.com \
    --cc=yocto@yoctoproject.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.