Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/minetest: don't depend on luajit
Date: Tue, 28 Jul 2020 23:47:50 +0200	[thread overview]
Message-ID: <6008628e-cb56-abee-86d2-1bb4ed95adfc@gmail.com> (raw)
In-Reply-To: <CADvTj4pBFitVFsWD1xkVTjFJ7=a2yDEycRX5J06KOi2YYE_EmQ@mail.gmail.com>

Hi James, all,

Le 28/07/2020 ? 22:44, James Hilliard a ?crit?:
> On Tue, Jul 28, 2020 at 5:48 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
>>
>> On Tue, 28 Jul 2020 04:17:26 -0600
>> James Hilliard <james.hilliard1@gmail.com> wrote:
>>
>>> On Tue, Jul 28, 2020 at 1:09 AM Thomas Petazzoni
>>> <thomas.petazzoni@bootlin.com> wrote:
>>>>
>>>> On Mon, 27 Jul 2020 14:56:21 -0600
>>>> James Hilliard <james.hilliard1@gmail.com> wrote:
>>>>
>>>>> Since minetest has a fallback to a bundled lua when luajit is not
>>>>> available we don't need to depend on luajit or any lua version at all.
>>>>
>>>> In general, I think we try to not use bundled libraries even when they
>>>> exist. If minetest needs a Lua interpreter, it should always use an
>>>> external Lua interpreter, I believe.
>>> From my understanding luajit is the only supported external lua
>>> interpreter for minetest. So I think it makes sense to not require
>>> a specific lua interpreter for flexibility.
>>
>> I don't understand your reply, as I was not talking about using other
>> Lua interpreters.
>>
>> What I'm saying is that if minetest has a mandatory dependency on
>> LuaJIT, then it should *always* use the external LuaJIT and never use
>> the bundled one. We prefer external libraries over bundled libraries in
>> general in the context of Buildroot.
> Oh, it doesn't have a mandatory LuaJIT dependency, the internal version
> is not LuaJIT but some bundled regular Lua 5.1 variant AFAIK.

When I packaged minetest, I looked at distribution packaging:

https://www.archlinux.org/packages/community/x86_64/minetest/
https://src.fedoraproject.org/rpms/minetest/blob/master/f/minetest.spec#_38
https://salsa.debian.org/games-team/minetest/-/blob/master/debian/control#L22

minetest use luajit when available.
Only Debian support liblua5.1 when luajit is not supported.

I'm not sure it worth the effort since minetest require x11 and libgl.

Best regards,
Romain


>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com

      reply	other threads:[~2020-07-28 21:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 20:56 [Buildroot] [PATCH 1/1] package/minetest: don't depend on luajit James Hilliard
2020-07-28  7:09 ` Thomas Petazzoni
2020-07-28 10:17   ` James Hilliard
2020-07-28 11:48     ` Thomas Petazzoni
2020-07-28 19:36       ` Yann E. MORIN
2020-07-28 20:44       ` James Hilliard
2020-07-28 21:47         ` Romain Naour [this message]

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=6008628e-cb56-abee-86d2-1bb4ed95adfc@gmail.com \
    --to=romain.naour@gmail.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