Openembedded Core Discussions
 help / color / mirror / Atom feed
From: timothy.t.orling@linux.intel.com
To: "OpenEmbedded Devel List"
	<openembedded-devel@lists.openembedded.org>,
	"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 08:56:55 -0700 (PDT)	[thread overview]
Message-ID: <33320.10.7.198.51.1465487815.squirrel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZnh1+tvznjgKKFrSoP-ie0vMD0m_5AtTEi0DcrpFjX6g@mail.gmail.com>

> On 9 June 2016 at 15:08, Philip Balister <philip@balister.org> wrote:
>
>> That said, what other layers use vala? If it leaves core, is there a
>> layer that can host it and support other layers using it without to much
>> trouble?
>>
>
> That's the key question really - can the support be extracted and added to
> eg meta-vala in some way?
>
> Ross

I use vala for clutter/cogl/weston/wayland development, although not in
any published public layers. Part of me hates to see it leave core, but a
well maintained layer is acceptable-ish. I know that vala-terminal in
meta-oe has been in and out of blacklist for quite a while now.

Cheers.

--Tim


  reply	other threads:[~2016-06-09 15:09 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 [this message]
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
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=33320.10.7.198.51.1465487815.squirrel@linux.intel.com \
    --to=timothy.t.orling@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