public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
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 19:32:33 +0000	[thread overview]
Message-ID: <26170862.UdgPXC9k0H@helios> (raw)
In-Reply-To: <20130212191902.GD3300@jama>

On Tuesday 12 February 2013 20:19:02 Martin Jansa wrote:
> On Mon, Feb 11, 2013 at 05:09:01PM +0000, Paul Eggleton wrote:
> > * tslib: OE-Core has the 1.0 release version, meta-oe has a git recipe
> > that is ahead of 1.0; the OE-Core version has two patches not in the
> > meta-oe version but that both have been merged upstream in the git
> > revision being used in the meta-oe version. There is no newer stable
> > release. What do we do here? Should we ask upstream (Chris) for a new
> > stable release?
> 
> tslib is also requested on devices where kernel driver returns too much
> noise, tslib can filter that, evdev needs separate filter like
> http://atrey.karlin.mff.cuni.cz/~metan/evfilter/
> but that isn't integrated in OE.

OK. I think the best course of action is to petition upstream for a stable 
release and then update OE-Core to that, then we can drop the recipe from 
meta-oe without ill effect.

> > * xserver-nodm-init: the two versions are quite distinct. Not sure I
> > understand the full history here but perhaps someone else can fill in the
> > blanks...?
> 
> The biggest difference is integrated xinput-calibrator and use of
> xserver-common_1.34.bb

So can you see a means for us to move this into OE-Core? Where are the points 
of conflict?

> > * 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.
>
> MySQL and PostgreSQL are not in oe-core so it cannot be replaced with
> simple PACKAGECONFIG option in oe-core recipe, but I also prefer to
> share such .bbappend somewhere instead of every distribution reinventing
> the wheel when trying to enable something as simple as db in qt.

We kind of discussed this already - PACKAGECONFIG can't work for this  anyway 
because at least for the database drivers it's a tri-state switch. At the 
moment all these bbappends really do is set QT_SQL_DRIVER_FLAGS, DEPENDS and 
set the correct include directory. This is not a particularly advanced 
mechanism, is unlikely to change, and I don't think it's too much to ask for 
this to be set in each distro layer. This is distro policy and should not be 
expressed in meta-oe.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  parent reply	other threads:[~2013-02-12 19:48 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
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 [this message]
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=26170862.UdgPXC9k0H@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@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