Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Andreas Oberritter <obi@opendreambox.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] qt4(-embedded).inc: create variables to ease overriding
Date: Tue, 22 May 2012 14:36:34 +0100	[thread overview]
Message-ID: <1823492.ykGXyerc6j@helios> (raw)
In-Reply-To: <4FBB9471.6040905@opendreambox.org>

On Tuesday 22 May 2012 15:28:17 you wrote:
> On 22.05.2012 14:51, Paul Eggleton wrote:
> > I think when we start getting to this level, especially because some of
> > these options imply extra DEPENDS, we should try to use PACKAGECONFIG
> > rather than specific variables.
> 
> Introducing PACKAGECONFIG is a more complex change. It can still be done
> in a later patch. 

It could be, but then we're introducing variables that will potentially go 
into people's distro configs only to take them away in the near future. I'm not 
especially keen on doing that.

> This patch just follows the semantics introduced by
> QT_SQL_DRIVER_FLAGS 

Right, and when that was introduced some time ago we did not have 
PACKAGECONFIG at all.

I realise this puts extra burden upon you, sorry about that. I can perhaps 
offer to do the PACKAGECONFIG changes for you, but I won't be able to get to 
them until next week at the earliest.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-05-22 13:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 11:37 [PATCH 1/2] qt4(-embedded).inc: create variables to ease overriding Andreas Oberritter
2012-05-22 11:37 ` [PATCH 2/2] qt4.inc: package keyboard drivers Andreas Oberritter
2012-05-22 12:51 ` [PATCH 1/2] qt4(-embedded).inc: create variables to ease overriding Paul Eggleton
2012-05-22 13:28   ` Andreas Oberritter
2012-05-22 13:36     ` Paul Eggleton [this message]
2012-05-22 14:10       ` Andreas Oberritter
2012-05-22 14:49         ` Paul Eggleton

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=1823492.ykGXyerc6j@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=obi@opendreambox.org \
    --cc=openembedded-core@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