From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] luarocks: refactor buildroot addon without patch
Date: Wed, 6 Feb 2019 13:04:04 +0100 [thread overview]
Message-ID: <20190206130404.61fade67@windsurf> (raw)
In-Reply-To: <20190120071945.11304-1-francois.perrad@gadz.org>
On Sun, 20 Jan 2019 08:19:45 +0100
Francois Perrad <fperrad@gmail.com> wrote:
> addon commands are actually implemented in luarocks 3.0.4,
> and they must be located in luarocks/cmd/external.
>
> so, it is useless to patch luarocks.
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> package/luarocks/0002-Buildroot-addon.patch | 361 --------------------
> package/luarocks/buildroot.lua | 326 ++++++++++++++++++
> package/luarocks/luarocks.mk | 6 +
> 3 files changed, 332 insertions(+), 361 deletions(-)
> delete mode 100644 package/luarocks/0002-Buildroot-addon.patch
> create mode 100644 package/luarocks/buildroot.lua
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-06 12:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 7:19 [Buildroot] [PATCH] luarocks: refactor buildroot addon without patch Francois Perrad
2019-02-06 12:04 ` Thomas Petazzoni [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=20190206130404.61fade67@windsurf \
--to=thomas.petazzoni@bootlin.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