[pkg-lua-devel] LuaJIT package.path?

[Enrico Tassi]

On Wed, Oct 16, 2013 at 09:52:13PM -0400, Peter Colberg wrote:
> To begin with the simple things: Should I prefix the gcc-lua* packages
> with lua-, i.e. lua-gcc-lua[-dev] and lua-gcc-lua-cdecl[-dev]? The
> first one is a plugin that adds a Lua interpreter to GCC, and the
> second one is useful only when loaded into that environment.

Hum, yes and now.  Source packages relevant to lua are better named
lua-foo-bar, but a source package can generate binary packages named in
a different way.  So lua-gcc (assuming it makes sense) may genate a
package called gcc-plugin-lua for example.

Btw, I have no experience for gcc packaging, but I may point you to the
gcc maintainers to generate packages that adhere to their standards.

dh-lua only helps for lua bindings (and luajit ones as soon as I fix
it).

> > For pure FFI modules, I guess it is easy once dh_lua has been fixed.
> > You can start by creating an account on alioth.debian.org, there we can
> > share a git repository for the packaging.
> 
> Ok, I made an account on alioth.
> 
> Later, where should I put the package repositories for your review?

There is a lua-create-gitbla... script in dh-lua, when you run it
it gives you both a local git repo with some stuff in there to start the
packaging and a shell script to be run on alioth.d.o to create the
origin remote repository.  You should be able to both create the repo
and push to it.  The I'd suggest to clone the pkg-lua repository, check
the README and add to the list your packages.

Cheers
-- 
Enrico Tassi