From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] Remove vala from oe-core
Date: Tue, 10 Nov 2015 15:29:58 +0100 [thread overview]
Message-ID: <5641FF66.7040705@pseudoterminal.org> (raw)
In-Reply-To: <5641FF6D.7000508@linux.intel.com>
On 11/10/2015 03:30 PM, Alexander Kanavin wrote:
> On 11/10/2015 04:22 PM, Jussi Kukkonen wrote:
>
>> There's currently no software built with vala in oe-core. That's not
>> great for vala (as it's not getting the automated testing that high
>> quality maintenance would require) and it's not great for oe-core (as
>> maintenance effort is better spent on components that _are_ used).
>>
>> Based on the above there's a feature request** to remove vala from
>> oe-core. Please comment here or on the bug if you think this is an
>> inappropriate idea or have suggestions.
>
> I have to say no. A lot of things in oe-core (libsoup for instance)
> come with an option to build vala bindings which in turn require
> native vapigen binary provided by vala package.
>
> Alex
>
Doesn't vala rely on GObject introspection, which is unsupported in OE?
next prev parent reply other threads:[~2015-11-10 14:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 14:22 [RFC] Remove vala from oe-core Jussi Kukkonen
2015-11-10 14:30 ` Alexander Kanavin
2015-11-10 14:29 ` Carlos Rafael Giani [this message]
2015-11-10 14:32 ` Alexander Kanavin
2015-11-10 14:50 ` Paul Eggleton
2015-11-10 15:06 ` Alexander Kanavin
2015-11-10 15:09 ` Paul Eggleton
2015-11-10 15:10 ` Burton, Ross
2015-11-10 15:19 ` Alexander Kanavin
2015-11-10 15:29 ` Otavio Salvador
2015-11-10 15:37 ` Alexander Kanavin
2015-11-10 15:39 ` Otavio Salvador
2015-11-10 16:25 ` Andreas Müller
2015-11-10 16:52 ` Otavio Salvador
2015-11-11 17:17 ` Richard Purdie
2015-11-11 17:38 ` Paul Eggleton
2015-11-12 11:18 ` Alexander Kanavin
2015-11-10 16:02 ` Martin Jansa
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=5641FF66.7040705@pseudoterminal.org \
--to=dv@pseudoterminal.org \
--cc=openembedded-core@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