<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 4 May 2017 at 10:18, Alexander Kanavin <span dir="ltr"><<a href="mailto:alexander.kanavin@linux.intel.com" target="_blank">alexander.kanavin@linux.intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><span class="gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Then meta-oe can continue to host libpng12.<br>
</blockquote>
<br></span>
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.<br></blockquote></div><br>For what it's worth, glmark2 was fixed in 2014:</div><div class="gmail_extra"><br></div><div class="gmail_extra"><a href="https://github.com/glmark2/glmark2/commit/499aa81a68fb4c8aac1c80f0d6a4cce05941c4cc">https://github.com/glmark2/glmark2/commit/499aa81a68fb4c8aac1c80f0d6a4cce05941c4cc</a></div><div class="gmail_extra"><br></div><div class="gmail_extra">glcompbench appears to be a fork of glmark, so the same fix should be trivial to apply.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>