On 05/05/2017 02:48 AM, Max Krummenacher wrote:
My concern at the moment is that anything removed now from oe-core will also be
removed
in oe-core pyro in the foreseeable future but the fix or relocation in meta-xyz
will
take time.
I'm fairly sure these patches will not make it to pyro - they are for
2.4 only. So everyone will have a few months to fix up their layers
before 2.4 is out.
Around the release of morty the same happened with libwnck3 which then made
morty fail for
anyone using libwnck3.
We probably should have a section in the release notes that lists
removed recipes. There are more layers than meta-oe, obviously they
can't be all fixed in sync with oe-core.
For what it's worth, glmark2 was fixed in 2014:
https://github.com/glmark2/glmark2/commit/499aa81a68fb4c8aac1c80f0d6a4cce05941c4cc
glcompbench appears to be a fork of glmark, so the same fix should be
trivial to apply.
I agree that the it is an easy fix for glmark2 and probably not that hard with
glcompbench,
nonetheless its sometimes nice to get a head start before things break.
I would rather remove glcompbench, as it was last updated in 2012
upstream. If someone objects, they should step up and actually maintain
the code and the recipe.
Generally, such fixes scale poorly in the absence of proper recipe
maintainers: we are lucky there's just two recipes, but what if there
was twenty?
Alex
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
