public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-devel@lists.openembedded.org,
	openembedded-core@lists.openembedded.org
Subject: Re: RFC: meta-oe appends and overlayed recipes
Date: Tue, 12 Feb 2013 13:38:42 +0000	[thread overview]
Message-ID: <2504845.PjsIqOo6Oo@helios> (raw)
In-Reply-To: <1360674605.30425.9.camel@ted>

On Tuesday 12 February 2013 13:10:05 Richard Purdie wrote:
> On Tue, 2013-02-12 at 09:24 +0000, Paul Eggleton wrote:
> > On Monday 11 February 2013 22:35:47 Richard Purdie wrote:
> > > On Mon, 2013-02-11 at 17:09 +0000, Paul Eggleton wrote:
> > > > *
> > > > meta-oe/recipes-qt/packagegroups/packagegroup-qte-toolchain-target.bba
> > > > ppe
> > > > nd This is adding qwt to the qte toolchain. As far as I am concerned
> > > > this
> > > > is a distro policy decision - Qwt is a third-party library that is not
> > > > part of Qt. I believe this should be moved to the layers for whichever
> > > > distros want this.
> > > > 
> > > > * meta-oe/recipes-qt/qt4/qt4-x11-free_4.8.4.bbappend
> > > > * meta-oe/recipes-qt/qt4/qt4-embedded_4.8.4.bbappend
> > > > These two add MySQL and PostgreSQL support to Qt and Qt/Embedded. I
> > > > see
> > > > this as a distro policy decision; these should move to the layers for
> > > > whichever distros want this. FWIW, this is particularly egregious if
> > > > you've already built Qt, then add meta-oe and find Qt is being
> > > > unexpectedly rebuilt.
> > > 
> > > If these were implemented as PACKAGECONFIG options, then distros would
> > > just need to set the appropriate PACKAGECONFIG for the package in the
> > > distro config and we wouldn't even need the appends...
> > 
> > The thing is the Qt configure options are a little more complicated - many
> > of them are three-state switches (enable built-in, enable as a plugin or
> > disabled). Thus we've opted to split the configuration options into
> > variables for each type. We don't get PACKAGECONFIG's DEPENDS handling,
> > but if we used PACKAGECONFIG we'd lose some flexibility.
> 
> Is there a way we can at least have it behave in a similar way to
> PACKAGECONFIG? Can those configuration variables be set from the
> distro?

Well, the default values are set using ?= in qt4.inc, so there's nothing 
stopping them from being set from the distro config.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2013-02-12 13:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-11 17:09 RFC: meta-oe appends and overlayed recipes Paul Eggleton
2013-02-11 17:50 ` Otavio Salvador
2013-02-12  8:38   ` Anders Darander
2013-02-11 22:35 ` Richard Purdie
2013-02-12  9:24   ` Paul Eggleton
2013-02-12 13:10     ` Richard Purdie
2013-02-12 13:38       ` Paul Eggleton [this message]
2013-02-12 10:24 ` [oe] " Burton, Ross
2013-02-12 10:38   ` Paul Eggleton
2013-02-12 16:43     ` Otavio Salvador
2013-02-12 20:51       ` Burton, Ross
2013-02-12 21:22         ` Martin Jansa
2013-02-12 21:36           ` Burton, Ross
2013-02-12 21:40             ` Otavio Salvador
2013-02-12 21:53             ` Eric Bénard
2013-02-12 22:02               ` Burton, Ross
2013-02-12 15:50   ` Ross Burton
2013-02-12 16:44     ` Otavio Salvador
2013-02-12 16:53       ` Paul Eggleton
2013-02-12 19:19 ` Martin Jansa
2013-02-12 19:31   ` [oe] " Otavio Salvador
2013-02-12 19:32   ` Paul Eggleton
2013-02-12 19:51     ` Martin Jansa
2013-02-12 20:40       ` Marcin Juszkiewicz
2013-02-12 19:32   ` [oe] " Chris Larson
2013-02-12 19:59     ` Mark Hatle

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=2504845.PjsIqOo6Oo@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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