All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Martin Jansa <martin.jansa@gmail.com>,
	OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: what means PROV_class-native = ""?
Date: Fri, 18 Jan 2013 13:57:36 -0800	[thread overview]
Message-ID: <50F9C550.5040507@linux.intel.com> (raw)
In-Reply-To: <20130118214509.GC29386@jama.palm1.palmone.com>

On 01/18/2013 01:45 PM, Martin Jansa wrote:
> On Fri, Jan 18, 2013 at 04:35:34PM -0500, Robert P. J. Day wrote:
>>
>>    perusing oe-core for examples to demonstrate the concept of
>> "PROVIDES =", and i ran across this in recipes-devtools/dpkg/dpkg.inc:
>>
>> PROV = "virtual/update-alternatives"
>> PROV_class-native = ""
>
> PROV is variable with no special meaning
> class-native is standard override for native recipe (like
> virtclass-native was before).
>
>> PROVIDES += "${PROV}"
>>
>>    i'm not sure what to make of that -- what's the purpose of assigning
>> to PROV, then subsequently assigning to PROVIDES, but with that
>>
>> PROV_class-native = ""
>>
>> line in between?  i did a grep and saw nothing else like it throughout
>> oe-core.
>>
I believe that idea is since it's PROVIDES += , not a straight 
assignment like = it's not a simple to override with the +=, so for the 
target case PROVIDE the virtual/u-a, but not for the native case of that 
package.

If it was a straight assignment (using =) the ${PROV} would not be needed.

Sau!

>> rday
>>
>> --
>>
>> ========================================================================
>> Robert P. J. Day                                 Ottawa, Ontario, CANADA
>>                          http://crashcourse.ca
>>
>> Twitter:                                       http://twitter.com/rpjday
>> LinkedIn:                               http://ca.linkedin.com/in/rpjday
>> ========================================================================
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>



  reply	other threads:[~2013-01-18 22:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 21:35 what means PROV_class-native = ""? Robert P. J. Day
2013-01-18 21:45 ` Martin Jansa
2013-01-18 21:57   ` Saul Wold [this message]
2013-01-18 22:06     ` Robert P. J. Day

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=50F9C550.5040507@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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.