From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] the fate of Vala in OE
Date: Fri, 10 Jun 2016 16:21:06 +0300 [thread overview]
Message-ID: <4128fb32-07bb-94d1-6b77-acb8984635fd@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZhrKJvg=m05_SUPktikELaDRq8gTvvtjfhaj_9Uq+vPw@mail.gmail.com>
On 06/09/2016 07:36 PM, Burton, Ross wrote:
> We do use Vala for internal gstreamer-related projects so I would
> volunteer to support it in oe-core.
>
>
> Would you volunteer to maintain it in a separate layer if possible? If
> nothing in core uses it and it can be maintained out of core then I
> think it should be moved out. Currently, vala support is in oe-core but
> nothing in oe-core uses it... so the autobuilder can't tell if it works.
How about?
1) vala compiler recipe and support for generating library bindings
stays in oe-core
2) we take care of updating the vala recipe to latest stable upstream
version
3) we make sure that vala recipe builds correctly and library bindings
are generated without error for libraries that are in oe-core
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'.
Alex
next prev parent reply other threads:[~2016-06-10 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 10:28 the fate of Vala in OE Alexander Kanavin
2016-06-09 14:08 ` [oe] " Philip Balister
2016-06-09 14:37 ` Burton, Ross
2016-06-09 15:56 ` timothy.t.orling
2016-06-09 15:59 ` Petr Nechaev
2016-06-09 16:36 ` Burton, Ross
2016-06-09 18:16 ` Martin Jansa
2016-06-10 0:04 ` Petr Nechaev
2016-06-10 13:21 ` Alexander Kanavin [this message]
2016-07-02 18:19 ` Tim Orling
2016-07-02 19:55 ` Khem Raj
2016-06-09 14:23 ` Carlos Rafael Giani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4128fb32-07bb-94d1-6b77-acb8984635fd@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox