From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Max Krummenacher <max.oss.09@gmail.com>,
"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/5] libpng12: remove the recipe
Date: Fri, 5 May 2017 12:16:09 +0300 [thread overview]
Message-ID: <1bed7e63-2374-21b5-e090-e3b111086ae9@linux.intel.com> (raw)
In-Reply-To: <1493941692.3022.18.camel@gmail.com>
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
next prev parent reply other threads:[~2017-05-05 9:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 13:11 [PATCH 1/5] liberation-fonts: update to 2.00.1 Alexander Kanavin
2017-05-03 13:11 ` [PATCH 2/5] packagegroup-core-lsb: do not include Qt4 anymore Alexander Kanavin
2017-05-03 13:11 ` [PATCH 3/5] libpng12: remove the recipe Alexander Kanavin
2017-05-03 18:41 ` Max Krummenacher
2017-05-03 18:58 ` Burton, Ross
2017-05-04 9:18 ` Alexander Kanavin
2017-05-04 9:54 ` Burton, Ross
2017-05-04 23:48 ` Max Krummenacher
2017-05-05 9:16 ` Alexander Kanavin [this message]
2017-05-07 23:46 ` Paul Eggleton
2017-05-05 10:10 ` Burton, Ross
2017-05-03 13:11 ` [PATCH 4/5] recipes-lsb4/perl: remove the recipes Alexander Kanavin
2017-05-04 10:49 ` Richard Purdie
2017-05-04 10:54 ` Alexander Kanavin
2017-05-04 11:16 ` Richard Purdie
2017-05-03 13:11 ` [PATCH 5/5] mailx: remove the recipe Alexander Kanavin
2017-05-03 13:31 ` ✗ patchtest: failure for "liberation-fonts: update to 2...." and 4 more Patchwork
2017-05-03 21:43 ` Paul Eggleton
2017-05-04 9:33 ` Alexander Kanavin
2017-05-04 10:07 ` Paul Eggleton
2017-05-04 10:16 ` Alexander Kanavin
2017-05-04 10:32 ` Peter Kjellerstedt
2017-05-04 10:32 ` Paul Eggleton
2017-05-04 15:36 ` Leonardo Sandoval
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=1bed7e63-2374-21b5-e090-e3b111086ae9@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=max.oss.09@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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