Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [v4 1/2] luainterpreter: create virtual package
Date: Mon, 30 Sep 2013 22:54:08 +0200	[thread overview]
Message-ID: <20130930225408.4ea0f858@skate> (raw)
In-Reply-To: <CA+-urNQZVaNvLwNUA_X6N7Ft2N0U1Yo6h+L__vNtHJfOZVPUSA@mail.gmail.com>

Dear Frank Hunleth,

On Mon, 30 Sep 2013 14:31:46 -0400, Frank Hunleth wrote:

> > +#############################################################
> > +#
> > +# Virtual package for luainterpreter
> > +#
> > +#############################################################
> > +
> > +LUAINTERPRETER_VERSION = 5.1
> 
> I was curious on your choice of version number for the virtual
> package. Is this intended to be used for API compatibility checks?
> 
> The reason that I'm asking is that I'm going to need to upgrade a
> project to Lua 5.2. There are enough API differences between Lua 5.1
> and 5.2 that it would be useful to use your patch set and add Lua 5.2
> as another luainterpreter. Using LUAINTERPRETER_VERSION sounds like
> one way of checking Lua API compatibility in other projects. Or did
> you have other thoughts?
> 
> Also, any word on the status of your patches?

Having a "version" attached to a virtual package does not make sense, I
believe.

If there are several incompatible versions of Lua that need to be
supported in Buildroot, then they must be packaged as separate
packages: lua, lua52 for example, like we're doing for python vs.
python4 and qt vs. qt5.

A virtual package should remain only have as dependencies packages that
provide the same API, i.e that interchangeable.

(Note: I have no knowledge about Lua specifically, those statements are
generic Buildroot rules.)

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2013-09-30 20:54 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 [this message]
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
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=20130930225408.4ea0f858@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox