<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 10, 2016 at 6:21 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 06/09/2016 07:36 PM, Burton, Ross wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We do use Vala for internal gstreamer-related projects so I would<br>
volunteer to support it in oe-core.<br>
<br>
<br>
Would you volunteer to maintain it in a separate layer if possible? If<br>
nothing in core uses it and it can be maintained out of core then I<br>
think it should be moved out. Currently, vala support is in oe-core but<br>
nothing in oe-core uses it... so the autobuilder can't tell if it works.<br>
</blockquote>
<br></span>
How about?<br>
<br>
1) vala compiler recipe and support for generating library bindings stays in oe-core<br>
<br>
2) we take care of updating the vala recipe to latest stable upstream version<br>
<br>
3) we make sure that vala recipe builds correctly and library bindings are generated without error for libraries that are in oe-core<br>
<br>
4) any other issues, such as compiler not working properly, or issues with bindings for things that are not in oe-core are handled by 'the community'.<br>
<br></blockquote><div><br></div><div>Excellent compromise. I volunteer to help with that.<br></div><div> --Tim<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Alex<div class="HOEnZb"><div class="h5"><br>
</div></div></blockquote></div><br></div></div>