From: Randy MacLeod <randy.macleod@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.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: Fri, 26 Jul 2013 12:08:15 -0400 [thread overview]
Message-ID: <51F29EEF.1020806@windriver.com> (raw)
In-Reply-To: <2462161.40E7azp51u@helios>
On 13-07-26 10:11 AM, Paul Eggleton wrote:
> On Thursday 25 July 2013 22:27:43 Martin Jansa wrote:
>> 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/recip
>>> es-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.
>
> I concur with Martin, if we're only talking about optional dependencies this
> should just be a case of adding the PACKAGECONFIG options to the recipes in
> OE-Core (or whereever they happen to be), with lua remaining in meta-oe.
I understand your reluctance to add bloat to oe-core but from a
users point of view a base distro should have a reasonable
collection of tools. I'll add lua to our internal layer since
we don't support all of meta-oe. We'll uprev and send meta-oe the
new recipe.
> However I am aware that lua may be a hard dependency for upcoming versions of
> stuff we do have in OE-Core (I can't recall which). We'll have to cross that
> bridge when we come to it.
Ok. Thanks for the feedback.
// Randy
>
> Cheers,
> Paul
>
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
WARNING: multiple messages have this Message-ID (diff)
From: Randy MacLeod <randy.macleod@windriver.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: koen@dominion.thruhere.net,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] Add lua to oe-core.
Date: Fri, 26 Jul 2013 12:08:15 -0400 [thread overview]
Message-ID: <51F29EEF.1020806@windriver.com> (raw)
In-Reply-To: <2462161.40E7azp51u@helios>
On 13-07-26 10:11 AM, Paul Eggleton wrote:
> On Thursday 25 July 2013 22:27:43 Martin Jansa wrote:
>> 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/recip
>>> es-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.
>
> I concur with Martin, if we're only talking about optional dependencies this
> should just be a case of adding the PACKAGECONFIG options to the recipes in
> OE-Core (or whereever they happen to be), with lua remaining in meta-oe.
I understand your reluctance to add bloat to oe-core but from a
users point of view a base distro should have a reasonable
collection of tools. I'll add lua to our internal layer since
we don't support all of meta-oe. We'll uprev and send meta-oe the
new recipe.
> However I am aware that lua may be a hard dependency for upcoming versions of
> stuff we do have in OE-Core (I can't recall which). We'll have to cross that
> bridge when we come to it.
Ok. Thanks for the feedback.
// Randy
>
> Cheers,
> Paul
>
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
next prev parent reply other threads:[~2013-07-26 16:08 UTC|newest]
Thread overview: 13+ 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
2013-07-26 14:11 ` Paul Eggleton
2013-07-26 14:11 ` [OE-core] " Paul Eggleton
2013-07-26 16:08 ` Randy MacLeod [this message]
2013-07-26 16:08 ` Randy MacLeod
2013-08-07 12:23 ` [oe] " Petr Štetiar
2013-08-07 12:23 ` Petr Štetiar
2013-08-07 12:38 ` [oe] " Laszlo Papp
2013-08-07 16:09 ` Marko Lindqvist
2013-08-07 16:09 ` [OE-core] " Marko Lindqvist
2013-08-07 18:30 ` [oe] " Khem Raj
2013-08-07 18:30 ` [OE-core] " 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=51F29EEF.1020806@windriver.com \
--to=randy.macleod@windriver.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.