 |
lua-l archive |
|
|
||
|
Adam D. Moss escribió:
... but I'd rather see it unanswered until the actual package/module system is in place, since some of the decisions made there will affect how the package distribution might actually happen.
I agree.
Once the user installs the LuaSocket module, fetching other (all-lua) modules and their dependancies could be done quite pleasantly in a variety of ways from within Lua itself... which is nice.
We developed a year ago an deployment system based on LuaSocket. After running a little piece of Lua code, the rest of the system (modules, dll's, etc) is kept up to date automagically. This project proved me that Lua is a good choice to distributed applications with centralized deployment and maintenance. But the idea can be also applied to installation of modules instead of deployment, as AK and you suggest.
Regards, Daniel