From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [UNSURE]Re: [v4 1/2] luainterpreter: create virtual package
Date: Tue, 1 Oct 2013 14:10:17 +0200 [thread overview]
Message-ID: <20131001141017.422ee8ab@skate> (raw)
In-Reply-To: <CAB0FRsspaq_BTykGrOPP=iyTxpm9Wu46wMvWgRHNDzSpj-XCkA@mail.gmail.com>
Dear Fran?ois Perrad,
On Tue, 1 Oct 2013 12:47:20 +0200, Fran?ois Perrad wrote:
> Lua 5.2.0 was released on December 2011 (see
> https://raw.github.com/fperrad/graph-versions/gh-pages/slides/lua.png).
> Since this, Lua module authors release new version which are
> compatible 5.1 and 5.2 (not a hard job, differences are small). But
> this process is not fast and not finished.
>
> So, I think Lua 5.1.x and 5.2.x can be handled by the same package
> with a choice (like gcc, binutils)
Ok. But then Lua packages that are not yet compatible with 5.2.x will
have to be marked "depends on !BR2_PACKAGE_LUA_5_2". Is this what you
had in mind?
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-01 12:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 8:35 [Buildroot] [v4 1/2] luainterpreter: create virtual package Francois Perrad
2013-08-14 8:35 ` [Buildroot] [v4 2/2] luajit: allow to build Lua extensions without lua Francois Perrad
2013-09-14 8:09 ` [Buildroot] [v4 1/2] luainterpreter: create virtual package François Perrad
2013-09-30 18:31 ` Frank Hunleth
2013-09-30 20:54 ` Thomas Petazzoni
2013-10-01 7:27 ` François Perrad
2013-10-01 7:31 ` Thomas Petazzoni
2013-10-01 10:47 ` [Buildroot] [UNSURE]Re: " François Perrad
2013-10-01 12:10 ` Thomas Petazzoni [this message]
2013-10-01 15:59 ` François Perrad
2013-10-01 16:06 ` Thomas Petazzoni
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=20131001141017.422ee8ab@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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.