Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 0/2] Adjust Luarocks support to per-package folder
Date: Mon, 19 Nov 2018 11:32:25 +0100	[thread overview]
Message-ID: <20181119103227.24726-1-thomas.petazzoni@bootlin.com> (raw)

Hello,

Based on Fran?ois Perrad's feedback, this small patch series reworks
how Luarocks is used to make it compatible with per-package
folders. It is sent as a separate series, because it can be applied
independently from the per-package series itself.

Thanks,

Thomas

Thomas Petazzoni (2):
  package/pkg-luarocks: drop flock at installation time
  package/luarocks: rework configuration file for per-package folders

 package/luarocks/0002-getenv-in-config.patch | 31 ++++++++++++++++++++
 package/luarocks/luarocks-br-config.lua      | 12 ++++++++
 package/luarocks/luarocks.mk                 | 21 +++++--------
 package/pkg-luarocks.mk                      |  2 +-
 4 files changed, 52 insertions(+), 14 deletions(-)
 create mode 100644 package/luarocks/0002-getenv-in-config.patch
 create mode 100644 package/luarocks/luarocks-br-config.lua

-- 
2.19.1

             reply	other threads:[~2018-11-19 10:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 10:32 Thomas Petazzoni [this message]
2018-11-19 10:32 ` [Buildroot] [PATCH next 1/2] package/pkg-luarocks: drop flock at installation time Thomas Petazzoni
2018-11-19 20:28   ` François Perrad
2018-11-19 20:46   ` Thomas Petazzoni
2018-11-19 10:32 ` [Buildroot] [PATCH next 2/2] package/luarocks: rework configuration file for per-package folders Thomas Petazzoni
2018-11-19 20:57   ` François Perrad
2018-11-20 11:02     ` Thomas Petazzoni
2018-11-21  8:23   ` François Perrad

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=20181119103227.24726-1-thomas.petazzoni@bootlin.com \
    --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