From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga09.intel.com ([134.134.136.24]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1U5GJp-0004OS-Dz; Tue, 12 Feb 2013 14:54:49 +0100 Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 12 Feb 2013 05:37:27 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.84,650,1355126400"; d="scan'208";a="261509804" Received: from unknown (HELO helios.localnet) ([10.252.120.87]) by orsmga001.jf.intel.com with ESMTP; 12 Feb 2013 05:38:43 -0800 From: Paul Eggleton To: Richard Purdie Date: Tue, 12 Feb 2013 13:38:42 +0000 Message-ID: <2504845.PjsIqOo6Oo@helios> Organization: Intel Corporation User-Agent: KMail/4.10 (Linux/3.5.0-23-generic; KDE/4.10.0; i686; ; ) In-Reply-To: <1360674605.30425.9.camel@ted> References: <2760168.9kFd94gL1F@helios> <1687588.iZvXQbhphA@helios> <1360674605.30425.9.camel@ted> MIME-Version: 1.0 Cc: openembedded-devel@lists.openembedded.org, openembedded-core@lists.openembedded.org Subject: Re: RFC: meta-oe appends and overlayed recipes X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2013 13:54:51 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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