All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/prosody: fix dependency
Date: Tue, 28 Jul 2020 22:25:11 +0200	[thread overview]
Message-ID: <20200728202511.GA16287@scaer> (raw)
In-Reply-To: <CAB0FRsvnTHG4=NhXFHYtO_vkC=B_Fvo-YhmhWqFVg4o97ONStQ@mail.gmail.com>

Fran?ois, All,

On 2020-07-28 11:21 +0200, Fran?ois Perrad spake thusly:
> Le?mar. 28 juil. 2020 ??09:21, Thomas Petazzoni < [1]thomas.petazzoni@bootlin.com> a ?crit?:
>   > LuaBitOp is not available with Lua 5.3
>   The commit log is probably not very clear. Indeed, if LuaBitOp is not
>   available with Lua 5.3, one would think you would need the external
>   BR2_PACKAGE_LUABITOP when using something else than 5.1, i.e the
>   opposite of what your change is doing.
> 
>   Shouldn't the commit log rather be:
> 
>   ? The luabitop functionality is available built-in in Lua 5.3 and
>   ? LuaJIT, so only Lua 5.1 needs the additional external luabitop
>   ? package.
> 
>   Could you confirm ?
> 
> bitwise operators are built-in in Lua 5.3,
> LuaBitOp is a built-in library in LuaJIT,
> so only Lua 5.1 needs the additional external LuaBitOp package.

OK, thanks for the explanations.

However, luabitop depends on !lua-5.3, and I see in your latest series
that you extended the dependency to !lua-5.4. Maybe we should also
fix that, no?

That is, we should have:

    config BR2_PACKAGE_LUABITOP
        depends on BR2_PACKAGE_LUA_5_1

However, you are saying (emphasize mine):

    "only Lua 5.1 **needs** the additional external LuaBitOp"

Does that mean that it can still be used with other versions of Lua?

That is, if we are using lua-5.3, and a package selects luabitop, will
this fail to build? To run? In other words, is it a problem if a pacakge
ends up using luabitop on another version of lua?

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2020-07-28 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28  6:21 [Buildroot] [PATCH] package/prosody: fix dependency Francois Perrad
2020-07-28  7:21 ` Thomas Petazzoni
2020-07-28  9:21   ` François Perrad
2020-07-28 20:25     ` Yann E. MORIN [this message]
2020-07-29 13:01       ` François Perrad
2020-08-08 21:48 ` 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=20200728202511.GA16287@scaer \
    --to=yann.morin.1998@free.fr \
    --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.