<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 17 June 2016 at 07:37, Jussi Kukkonen <span dir="ltr"><<a href="mailto:jussi.kukkonen@intel.com" target="_blank">jussi.kukkonen@intel.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=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>> That's certainly a good argument for putting the old vte in meta-oe.<br>
<br>
</span>The meta-oe layers generally have a higher priority than oe-core, so<br>
having an older version in meta-oe and a newer version in oe-core can<br>
lead to unexpected results.<br>
<div><div><br></div></div></blockquote><div><br></div></span><div>As far as I know the versions are parallel installable so that should not be a problem. I removed the old one as there was no need for it in oe-core. Should have checked meta-oe as well, but there were just so many moving parts to juggle here... The right solution should indeed be to add the old one into the layer where it's needed.</div></blockquote><div><br></div><div>If they're parallel installable then the resurrected vte could have the version in the PN so both can be installed at the same time, until everything has moved to the modern vte and the old one can die for good.</div><div><br></div><div>Ross</div></div></div></div>