<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 17 June 2016 at 16:33, Mark Asselstine <span dir="ltr"><<a href="mailto:mark.asselstine@windriver.com" target="_blank">mark.asselstine@windriver.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="">On June 16, 2016 18:10:09 Andre McCurdy wrote:<br>
> On Thu, Jun 16, 2016 at 2:47 PM, Burton, Ross <<a href="mailto:ross.burton@intel.com">ross.burton@intel.com</a>> wrote:<br>
> > On 16 June 2016 at 21:49, Mark Asselstine <<a href="mailto:mark.asselstine@windriver.com">mark.asselstine@windriver.com</a>><br>
> ><br>
> > wrote:<br>
> >> While waiting to hear back about my inquiry I did take some<br>
> >> time to put together this patch that allows things that<br>
> >> require the older vte to continue to build. Since xfce4-terminal<br>
> >> lives in meta-openembedded this might make more sense to carry<br>
> >> over there. I am sure folks will have an opinion so sending this<br>
> >> out as an RFC.<br>
> ><br>
> > That's certainly a good argument for putting the old vte in meta-oe.<br>
><br>
> 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>
<br>
</span>This should not be an issue. My change has the old recipe renamed with the API<br>
version so the old version becomes referenced by 'vte-0.0' (per the commit log<br>
the 0.0 is consistent with the API versioning upstream). So recipes which<br>
require the old version, like xfce4-terminal, have to have their DEPENDS<br>
adjusted accordingly. There should be no surprises.<br>
<br>
I will have a closer look today to ensure nothing in oe-core is requiring the<br>
old version and if not I will prepare a patch for meta-oe since that seems to<br>
be the general agreement for a home for this. I need to do some further checks<br>
and runtime tests but I will get this out shortly. In the meantime anyone else<br>
running in to the build failure can exploit the RFC patch.</blockquote><div><br></div><div>Thanks Mark. I can confirm that nothing in oe-core needs the old vte.</div><div><br></div><div>As a sidenote in case you're looking at the vte users in oe-core: I notice I didn't include a patch for qemu yet. The situation there is that our qemu version works fine with the new vte but might still need a small <a href="http://configure.ac">configure.ac</a> patch in addition to updated PACKAGECONFIG line. I'll include this in my next patchset.</div><div><br></div><div>- Jussi</div><div><br></div><div><br></div><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=""><font color="#888888">
Mark<br>
</font></span><div class=""><div class="h5"><br>
><br>
> > Ross<br>
> ><br>
> > --<br>
> > _______________________________________________<br>
> > Openembedded-core mailing list<br>
> > <a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
> > <a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
<br>
--<br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</div></div></blockquote></div><br></div></div>