On 2016-06-10 10:41, Martin Jansa wrote:
You're reading it from wrong side.
This shows what vala-native needs, not what needs vala-native.
Yes, I realized that :-(
The actual list is smaller, but still important:
"gcr" -> "vala-native" [style=solid]
"gcr" -> "vala" [style=solid]
"libsecret" -> "vala-native" [style=solid]
"libsecret" -> "vala" [style=solid]
Both of those packages are in OE-core (meta/recipes-gnome)
On Fri, Jun 10, 2016 at 10:35 AM, Gary Thomas <[email protected]> wrote:
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
------------------------------------------------------------
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel
