Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Carlos Rafael Giani <dv@pseudoterminal.org>
To: openembedded-core@lists.openembedded.org
Subject: Re: the fate of Vala in OE
Date: Thu, 9 Jun 2016 16:23:15 +0200	[thread overview]
Message-ID: <57597BD3.8070104@pseudoterminal.org> (raw)
In-Reply-To: <cfce0a18-6762-9da4-1f4a-1969a912bf50@linux.intel.com>

On 2016-06-09 12:28, Alexander Kanavin wrote:
> Hello,
>
> I'd like to propose the removal of Vala recipe and support for 
> generating Vala bindings from oe-core. The only software that is 
> written in Vala and makes sense in embedded environment is Rygel (an 
> implementation of various UPnP AV services), and even that can be 
> compiled from intermediate C sources without a need for Vala compiler 
> or bindings. The only benefit from compiling from Vala source would be 
> that Rygel could be more easily patched - and I think that doesn't 
> really justify maintaining the full Vala stack.
>
> Thoughts?
>
> Alex

The benefit of easy patching is considerable. If you only have the C 
sources, then the patches have to be done between versions of that 
generated C code. The resulting patches are often big and unreadable.

I was actually happy to see g-i added to OE-core so we can get rid of 
some custom C-source patches for Rygel and just patch the Vala code 
directly instead. Removing vala would nullify this benefit.


      parent reply	other threads:[~2016-06-09 14:23 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
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 [this message]

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=57597BD3.8070104@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