Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Simon Busch <morphis@gravedo.de>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] mesa: add PACKAGECONFIG_DISTRO variable for distro specific options
Date: Mon, 19 Aug 2013 21:00:28 +0200	[thread overview]
Message-ID: <52126B4C.5040004@gravedo.de> (raw)
In-Reply-To: <8886217.PuVShUglzT@helios>

Am 19.08.2013 18:58, schrieb Paul Eggleton:
> On Monday 19 August 2013 18:28:02 Simon Busch wrote:
>> Am 19.08.2013 18:09, schrieb Phil Blundell:
>>> On Mon, 2013-08-19 at 18:04 +0200, Simon Busch wrote:
>>>> In some cases as distribution just wants to extend the default
>>>> PACKAGECONFIG instead of rewriting it completely. Therefor having a
>>>> PACKAGECONFIG_DISTRO variable which is empty by default and included in
>>>> PACKAGECONFIG helps a lot.
>>>
>>> Can't those distros just use PACKAGECONFIG_append?
>>
>> They can. I tried with PACKAGECONFIG += which didn't worked and I
>> thought it would be the same with PACKAGECONFIG_append cause of
>> PACKAGECONFIG being weak assignment in mesa.inc. But as it seems +=
>> takes higher than the weak assignment and overrides PACKAGECONFIG where
>> _append only appends.
> 
> It's being set in the recipe with ??= which is the weakest form of assignment, 
> so this behaviour is expected. I just tested this in local.conf and it works:
> 
> PACKAGECONFIG_append_pn-mesa = " something"
> 
> BTW, outside of a recipe (or bbappend) you should always use a pn- override 
> with PACKAGECONFIG or you'll be affecting more than just the recipe you intend 
> to.

Thank you very much for the good explanation.

regards,
Simon

-- 
Simon Busch - http://mm.gravedo.de/blog/


      reply	other threads:[~2013-08-19 19:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-19 16:04 [PATCH] mesa: add PACKAGECONFIG_DISTRO variable for distro specific options Simon Busch
2013-08-19 16:09 ` Phil Blundell
2013-08-19 16:28   ` Simon Busch
2013-08-19 16:58     ` Paul Eggleton
2013-08-19 19:00       ` Simon Busch [this message]

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=52126B4C.5040004@gravedo.de \
    --to=morphis@gravedo.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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