<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 12 November 2015 at 18:59, Martin Jansa <span dir="ltr"><<a href="mailto:martin.jansa@gmail.com" target="_blank">martin.jansa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> > There is already enough meta-oe bloat moved from oe-core:<br>
> ><br>
> > <a href="http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112665.html" rel="noreferrer" target="_blank">http://lists.openembedded.org/pipermail/openembedded-core/2015-November/112665.html</a><br>
> ><br>
> > WARN: qt-mobility-embedded: qt-mobility-embedded rdepends on glib-2.0, but<br>
> > it isn't a build dependency?<br>
><br>
> If increasing bloat is a problem, why do recipes in meta-oe need to be<br>
> maintained indefinitely? Old cruft can be dropped from meta-oe, just as it<br>
> is dropped from oe-core. Just ask the public if it's ok, set a timeframe,<br>
> and do it.<br>
><br>
> qt-mobility in particular has been dead for several years, and doesn't<br>
> even have official upstream tarballs anymore. Why spend time fixing it?<br>
<br>
</span>That's why there is increasing number of PNBLACKLISTs with each release.<br>
<div class="HOEnZb"></div></blockquote></div><br>The recipes were removed from oe-core as they're dead upstream, and basically as a courtesy moved to meta-oe so anyone still using dead software can still build it. If they're just bitrotting and literally nobody is using the recipes then they should be removed: meta-oe isn't a historical archive that you're expected to maintain for the next decade.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>