From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2419] New: Add a bundle of Lua modules
Date: Sun, 22 Aug 2010 18:39:36 +0000 (UTC) [thread overview]
Message-ID: <bug-2419-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=2419
Summary: Add a bundle of Lua modules
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: francois.perrad at gadz.org
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created attachment 2365
--> https://bugs.busybox.net/attachment.cgi?id=2365
tarball
The first patch create the directory package/modules-lua,
and moves all actual Lua modules into.
Each of others patches adds a Lua module/library.
All these modules are available via LuaRocks, the Lua package installer for
no cross-compiling system.
(see http://luarocks.org/repositories/rocks/)
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2010-08-22 18:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-22 18:39 bugzilla at busybox.net [this message]
2010-12-06 14:21 ` [Buildroot] [Bug 2419] Add a bundle of Lua modules bugzilla at busybox.net
2011-03-02 23:02 ` bugzilla at busybox.net
2011-04-28 14:29 ` bugzilla at busybox.net
2011-04-28 14:32 ` bugzilla at busybox.net
2011-04-28 21:41 ` bugzilla at busybox.net
2011-04-29 12:13 ` bugzilla at busybox.net
2011-04-29 23:31 ` bugzilla at busybox.net
2011-05-29 8:24 ` bugzilla at busybox.net
2012-08-31 15:11 ` bugzilla at busybox.net
2013-05-26 8:09 ` bugzilla at busybox.net
2013-05-27 8:39 ` bugzilla at busybox.net
2014-02-08 20:49 ` bugzilla at busybox.net
2014-02-10 18:00 ` bugzilla at busybox.net
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=bug-2419-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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