From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] the fate of Vala in OE
Date: Fri, 10 Jun 2016 10:35:55 +0200 [thread overview]
Message-ID: <575A7BEB.1060808@mlbassoc.com> (raw)
In-Reply-To: <CAHPquwPKh0hgOuvHvB0KYVfU0PhtR_sZ8vKO8EgH_YgsZrwtkA@mail.gmail.com>
On 2016-06-10 02:04, Petr Nechaev wrote:
> I can see that libsecret in oe-core depends on vala though for testing only.
>
> If moving to meta-oe is community's decision, I will prepare the patch.
>
It looks like a lot of things need vala (or more precisely vala-native).
I just tried a build which included meta-browser (I know this isn't OE-core
but _is_ very common) and saw this dependency chain:
"vala-native" -> "libxslt-native" [style=solid]
"vala-native" -> "glib-2.0-native" [style=solid]
"vala-native" -> "autoconf-native" [style=solid]
"vala-native" -> "automake-native" [style=solid]
"vala-native" -> "libtool-native" [style=solid]
"vala-native" -> "gnu-config-native" [style=solid]
"vala-native" -> "pkgconfig-native" [style=solid]
"vala-native" -> "flex-native" [style=solid]
"vala-native" -> "bison-native" [style=solid]
In this case, I think vala (vala-native) deserves OE-core status.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-06-10 8:36 UTC|newest]
Thread overview: 28+ 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 ` Philip Balister
2016-06-09 14:08 ` [oe] " Philip Balister
2016-06-09 14:37 ` [OE-core] " Burton, Ross
2016-06-09 14:37 ` [oe] " Burton, Ross
2016-06-09 15:56 ` [OE-core] " timothy.t.orling
2016-06-09 15:56 ` [oe] " timothy.t.orling
2016-06-09 15:59 ` [OE-core] " Petr Nechaev
2016-06-09 15:59 ` [oe] " Petr Nechaev
2016-06-09 16:36 ` [OE-core] " Burton, Ross
2016-06-09 16:36 ` [oe] " Burton, Ross
2016-06-09 18:16 ` [OE-core] " Martin Jansa
2016-06-09 18:16 ` [oe] " Martin Jansa
2016-06-10 0:04 ` [OE-core] " Petr Nechaev
2016-06-10 0:04 ` [oe] " Petr Nechaev
2016-06-10 8:35 ` Gary Thomas [this message]
2016-06-10 8:41 ` [OE-core] " Martin Jansa
2016-06-10 10:10 ` Gary Thomas
2016-06-10 13:16 ` Alexander Kanavin
2016-06-10 13:21 ` Alexander Kanavin
2016-06-10 13:21 ` [oe] " Alexander Kanavin
2016-07-02 18:19 ` [OE-core] " Tim Orling
2016-07-02 18:19 ` [oe] " Tim Orling
2016-07-02 19:55 ` [OE-core] " Khem Raj
2016-07-02 19:55 ` [oe] " Khem Raj
2016-06-10 13:09 ` [OE-core] " Alexander Kanavin
2016-06-10 13:06 ` Alexander Kanavin
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=575A7BEB.1060808@mlbassoc.com \
--to=gary@mlbassoc.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.