From: Max Krummenacher <max.oss.09@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/5] libpng12: remove the recipe
Date: Fri, 05 May 2017 01:48:12 +0200 [thread overview]
Message-ID: <1493941692.3022.18.camel@gmail.com> (raw)
In-Reply-To: <CAJTo0LYDLu5zPf1EKrJKS-Hw-C=MumF8QXej_+i958AyWqy4CA@mail.gmail.com>
Am Donnerstag, den 04.05.2017, 10:54 +0100 schrieb Burton, Ross:
> On 4 May 2017 at 10:18, Alexander Kanavin <alexander.kanavin@linux.intel.com
> > wrote:
>
> > Then meta-oe can continue to host libpng12.
> > >
> >
> > I actually think allowing those recipes to fail and blacklisting them is
> > better. Moving libpng12 to meta-oe is the lazy way out; the proper way to
> > deal with such regressions is to look at the actual recipes, what they do,
> > why they need such an old version of libpng, and whether they should be
> > updated or removed from meta-oe altogether. The only way to get people to
> > do this real maintenance work is to break the build for them, sadly. I
> > cannot take on maintaining things in meta-oe in this way, I have to draw
> > the line somewhere, and this is it.
> >
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.
Around the release of morty the same happened with libwnck3 which then made morty fail for
anyone using libwnck3.
>
> 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.
Max
> Ross
next prev parent reply other threads:[~2017-05-04 23:48 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 [this message]
2017-05-05 9:16 ` Alexander Kanavin
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=1493941692.3022.18.camel@gmail.com \
--to=max.oss.09@gmail.com \
--cc=alexander.kanavin@linux.intel.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