Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: koen@dominion.thruhere.net,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>,
	openembedded-core@lists.openembedded.org
Subject: Re: Add lua to oe-core.
Date: Thu, 25 Jul 2013 22:27:43 +0200	[thread overview]
Message-ID: <20130725202743.GB3280@jama> (raw)
In-Reply-To: <51F18346.2@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

On Thu, Jul 25, 2013 at 03:57:58PM -0400, Randy MacLeod wrote:
> 
> I've found that many projects use the lua scripting language.
> I'd like to move it from meta-oe to oe-core:
> 
>  
> http://cgit.openembedded.org/cgit.cgi/meta-openembedded/tree/meta-oe/recipes-devtools/lua/lua5.1_5.1.5.bb?h=master
> 
> http://www.lua.org/about.html
> 
> lua-5.2.2 is current, see: http://www.lua.org/download.html
> so we'd likely uprev and send that version.
> 
> rpm and lighttpd could (would?) optionally depend on lua.
> 
> oe-core.git $ grep -r lua * | egrep -v 'valuat|valuable|uargp|rpm'
> meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb:
>               --without-lua \
> 
> Any comments pro or con before we do the uprev, testing and send
> a commit?

2 recipes which would optionally depend on it doesn't make it good
"core" component IMHO.

But uprev, few PACKAGECONFIGs and more testing would be nice.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-07-25 20:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 19:57 Add lua to oe-core Randy MacLeod
2013-07-25 20:27 ` Martin Jansa [this message]
2013-07-26 14:11   ` Paul Eggleton
2013-07-26 16:08     ` Randy MacLeod
2013-08-07 12:23 ` [oe] " Petr Štetiar
2013-08-07 12:38   ` Laszlo Papp
2013-08-07 16:09   ` Marko Lindqvist
2013-08-07 18:30   ` Khem Raj

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=20130725202743.GB3280@jama \
    --to=martin.jansa@gmail.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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