Add lua to oe-core.
I've found that many projects use the lua scripting language. I'd like to move it from meta-oe to oe-core:
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?
Signature · 2 lines
# Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350
Quoted 12 lines · Randy MacLeod
I've found that many projects use the lua scripting language. I'd like to move it from meta-oe to oe-core:
lua-5.2.2 is current, see: http://www.lua.org/download.html
so we'd likely uprev and send that version.
Quoted 8 lines
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.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 19 lines · On Thursday 25 July 2013 22:27:43 Martin Jansa wrote:
Quoted 18 lines · Randy MacLeod
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=masterlua-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 \
Quoted 7 lines
Quoted 2 lines
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.
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.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 23 lines · Paul Eggleton
Quoted 22 lines · On Thursday 25 July 2013 22:27:43 Martin Jansa wrote:
Quoted 20 lines · Randy MacLeod
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=masterlua-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?
Quoted 8 lines
Quoted 4 lines
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.
Quoted 3 lines
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
Quoted 4 lines
Cheers,
Paul
Signature · 2 lines
# Randy MacLeod. SMTS, Linux, Wind River Direct: 613.963.1350
Randy MacLeod <[email protected]> [2013-07-25 15:57:58]:
Quoted 2 lines
lua-5.2.2 is current, see: http://www.lua.org/download.html
so we'd likely uprev and send that version.
Just FYI Lua 5.2 has quite a lot of changes to Lua 5.1[1]. So I wouldn't consider it as an drop-in replacement for Lua 5.1. Simply said it's not compatible out of the box.
Quoted 3 lines
oe-core.git $ grep -r lua * | egrep -v 'valuat|valuable|uargp|rpm' meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb:
--without-lua \
For example lighttpd uses Lua 5.1.
1. http://www.corsix.org/content/look-lua-52-work3
-- ynezz
I support updating lua if nothing breaks.
Quoted 23 lines · Petr Štetiar
Randy MacLeod <[email protected]> [2013-07-25 15:57:58]:
Quoted 2 lines
lua-5.2.2 is current, see: http://www.lua.org/download.html
so we'd likely uprev and send that version.Just FYI Lua 5.2 has quite a lot of changes to Lua 5.1[1]. So I wouldn't consider it as an drop-in replacement for Lua 5.1. Simply said it's not compatible out of the box.
Quoted 3 lines
oe-core.git $ grep -r lua * | egrep -v 'valuat|valuable|uargp|rpm' meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb:
--without-lua \For example lighttpd uses Lua 5.1.
1. http://www.corsix.org/content/look-lua-52-work3
-- ynezz
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
Quoted 8 lines · Petr Štetiar
Randy MacLeod <[email protected]> [2013-07-25 15:57:58]:
Quoted 2 lines
lua-5.2.2 is current, see: http://www.lua.org/download.html
so we'd likely uprev and send that version.Just FYI Lua 5.2 has quite a lot of changes to Lua 5.1[1]. So I wouldn't consider it as an drop-in replacement for Lua 5.1. Simply said it's not compatible out of the box.
Yes, 5.1 and 5.2 are incompatible to extend that there simply is no
way to do some things so that it would work with both (5.1 has it one way, 5.2 has it another way, and neither understand the other) It can take some effort to switch application from using lua 5.1 to using lua 5.2.
- ML
Quoted 8 lines · Petr Štetiar
Randy MacLeod <[email protected]> [2013-07-25 15:57:58]:
Quoted 2 lines
lua-5.2.2 is current, see: http://www.lua.org/download.html
so we'd likely uprev and send that version.Just FYI Lua 5.2 has quite a lot of changes to Lua 5.1[1]. So I wouldn't consider it as an drop-in replacement for Lua 5.1. Simply said it's not compatible out of the box.
5.2 is not ABI compatible with 5.1 see
http://www.lua.org/manual/5.2/manual.html#8
so you can add a new recipe for 5.2 on
the same lines at 5.1 but don't delete 5.1
Quoted 14 lines
Quoted 4 lines
oe-core.git $ grep -r lua * | egrep -v 'valuat|valuable|uargp|rpm' meta/recipes-extended/lighttpd/lighttpd_1.4.32.bb:
--without-lua \For example lighttpd uses Lua 5.1.
1. http://www.corsix.org/content/look-lua-52-work3
-- ynezz
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core