Hi there,
I am interested in creating rockspecs and publishing some parts (or all
parts) of lubyk. At least, I want to have "dub" (C++ binding generator) and
the auto-doc tool used by lubyk (http://doc.lubyk.org/lk.Doc.html).
I have a couple of questions which might become show stoppers...
1. How do you handle runtime dependency between modules (version matching) ?
2. How to deal with namespace conflicts ? For example, I have a "zmq"
module that is very different from luazmq. What happens when someone does:
local zmq = require"zmq"
I could prefix all modules with "lubyk-zmq", so that the above require
would be:
local zmq = require"lubyk-zmq"
3. Autoload. Lubyk uses an auto-load system so when lubyk users do (without
other requires then "require 'lubyk'":
local s = zmq.Socket(...)
This automagically loads "zmq" and "zmq.Socket". I feel that this should
work without too many issues.
4. Common files needed in "includes" and build. Multiple modules use the
"Fifo" and msgpack code to transform OS threads into pipes. Does this mean
that I need to copy these common files in each rock sources ?
Thanks for your help,
Gaspard
------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete
for recognition, cash, and the chance to get your game on Steam.
$5K grand prize plus 10 genre and skill prizes. Submit your demo
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
Luarocks-developers mailing list
Luarocks-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/luarocks-developers
