From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Konstantin Ripak <konstantin.ripak@cogentembedded.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] the fate of Vala in OE
Date: Thu, 9 Jun 2016 20:16:13 +0200 [thread overview]
Message-ID: <20160609181613.GB2586@jama> (raw)
In-Reply-To: <CAJTo0LZhrKJvg=m05_SUPktikELaDRq8gTvvtjfhaj_9Uq+vPw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]
On Thu, Jun 09, 2016 at 05:36:32PM +0100, Burton, Ross wrote:
> On 9 June 2016 at 16:59, Petr Nechaev <petr.nechaev@cogentembedded.com>
> 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.
It's used by couple recipes in meta-oe and other layers which already
depend on meta-oe:
meta-multimedia, meta-gnome, meta-efl, meta-fso
so if you want to move it out from oe-core, then it should be returned
to meta-oe (from where it was moved to oe-core a while back with midori):
commit 6f642a51dc98b0a8a20b2d0a6bfe6917e9f2091f
Author: Paul Eggleton <paul.eggleton@linux.intel.com>
Date: Wed Aug 28 10:43:25 2013 +0000
classes/vala: remove
This is now in OE-Core as of 807285c751862aaa775db5a13293007bfb3c29df.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
commit ad185f4494fff1254bfa167d6715db7be5a2de04
Author: Paul Eggleton <paul.eggleton@linux.intel.com>
Date: Wed Aug 28 10:43:24 2013 +0000
vala: remove
This is now in OE-Core as of 649b48557d8702daaf4f28482848ab0b07abed83.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-06-09 18:15 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 [this message]
2016-06-10 0:04 ` Petr Nechaev
2016-06-10 13:21 ` Alexander Kanavin
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=20160609181613.GB2586@jama \
--to=martin.jansa@gmail.com \
--cc=konstantin.ripak@cogentembedded.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