From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Making the Luarocks integration compatible with per-package folders
Date: Mon, 19 Nov 2018 11:20:29 +0100 [thread overview]
Message-ID: <20181119112029.5397e08a@windsurf.home> (raw)
In-Reply-To: <CAB0FRsveCsQ+Vuk4J4e_LbTRHYQ1prvfQ4+RODP0ZgB9KZYW8w@mail.gmail.com>
Hello Fran?ois,
On Fri, 16 Nov 2018 21:42:20 +0100, Fran?ois Perrad wrote:
> The use of environment variables is doable (I did some experiments in
> master branch).
> The config file is written in plain Lua, but loaded in a sandbox
> environment.
> A small patch of luarocks (see attachment) is required for allowing the
> getenv function.
Thanks a lot for all this feedback, it was extremely useful, and I
could come up with a set of patches that address the problem. I will
send it to the mailing list and Cc you.
Again, thanks a lot for your support!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-11-19 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 16:06 [Buildroot] Making the Luarocks integration compatible with per-package folders Thomas Petazzoni
2018-11-16 20:42 ` François Perrad
2018-11-19 10:20 ` 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=20181119112029.5397e08a@windsurf.home \
--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