From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/lua-debug: new package
Date: Fri, 28 Dec 2018 16:16:18 +0100 [thread overview]
Message-ID: <20181228161618.39acb1bd@windsurf> (raw)
In-Reply-To: <CAB0FRssfuEbz=KUdcpaaoeJd+a1Yoo-URrjvFf1N8L3Csxdr1Q@mail.gmail.com>
Hello Fran?ois,
Thanks a lot for your feedback on this series.
On Fri, 28 Dec 2018 15:32:39 +0100, Fran?ois Perrad wrote:
> > +# lua-debug
>
> This rock uses the namespace std.
> So, in order to avoid future name collision, it must be named lua-std-debug
Just for my own understanding, could you give a few more details about
this? We don't have any package today named lua-std-<something>, so I'm
interested in understanding this "namespace std" thing and the
namespace pollution issue.
Also, is your automated luarocks package generation logic
(http://patchwork.ozlabs.org/patch/1015895/) going to name such a
package lua-std-debug and not lua-debug ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-12-28 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 0:37 [Buildroot] [PATCH 1/3] package/lua-debug: new package james.hilliard1 at gmail.com
2018-12-28 0:37 ` [Buildroot] [PATCH 2/3] package/lua-normalize: " james.hilliard1 at gmail.com
2018-12-28 14:33 ` François Perrad
2018-12-28 0:37 ` [Buildroot] [PATCH 3/3] package/luaposix: bump version to 34.0.4 james.hilliard1 at gmail.com
2018-12-28 14:38 ` François Perrad
2018-12-28 14:32 ` [Buildroot] [PATCH 1/3] package/lua-debug: new package François Perrad
2018-12-28 15:16 ` Thomas Petazzoni [this message]
2018-12-28 16:09 ` 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=20181228161618.39acb1bd@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 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.