Re: RFC: meta-oe appends and overlayed recipes

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1769 bytes --]

On Tue, Feb 12, 2013 at 07:32:33PM +0000, Paul Eggleton wrote:
> 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.

Agreed,
 
> > > * 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?

xinput-calibrator is now being reworked by Andreas so we should at least
wait for this rework to settle down and xserver-common is similar to
formfactor, a bit more flexible but a lot worse to maintain for new
MACHINES (FWIW all local patches are waiting in florian mbox).

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]