3 ms·
Do you actually do that manually? Why isn't there a script for that? It should be a part of the automated process. Much better doing it once as an automatic ste
by acqq 12y ago
Do you actually do that manually? Why isn't there a script for that? It should be a part of the automated process. Much better doing it once as an automatic step than writing everywhere in your sources:
somethingbig/somethingbig
every time you use somethingbig. And that step should also zip the modules, I believe.
The behavior of require, as I'd like it:
require X first looks in the directory X, for module X. If there is no such, it opens modules.zip and reads module X from there. If internally in the ZIP there were a subdir for every module, I don't care, as long as I don't have to type that fact every time.
modules.zip would be constructed automatically. Whoever wants to tweak some specific module can unpack it in the separate directory.
- ANTSANTS 12y agoHaving reread the Lua manual, `require "lib"' can easily be made to execute `require "luapower/lib/lib.lua"' by adding "luapower/?/?.lua" to LUA_PATH. This is the way the standard /usr/local/lua libraries are require'd. Now I cannot think of a single explanation for why luapower works the way it does.
- acqq 12y agoI'd prefer modifying require to not need a new entry to the ENV var for every used module. It is a huge waste of ENV.
- ANTSANTS 12y agohttp://www.lua.org/pil/8.1.html http://www.lua.org/pil/8.1.html > To determine its path, require first checks the global variable LUA_PATH. If the value of LUA_PATH is a string, that string is the path. Otherwise, require checks the environment variable LUA_PATH. Even if you needed to modify an environment variable, I still think that would be preferable to creating yet another package manager and fracturing the Lua userbase further.
- acqq 12y agoAs a user, I want to "just use it" and the binary to "know" where the stuff of the module is without me having to hold its hand. Specifically, I don't want to know about LUA_PATH unless to use it to point to the single dir where I put my own modules.
- ANTSANTS 12y agoYour concern doesn't make any sense. Any package manager has to modify LUA_PATH in order for require to work with it in that way (unless it installs libs in /usr/local/lua, which requires admin privileges and isn't portable to Windows). luapower surely does this already, adding "luapower/?/?.lua" to the path instead of "luapower/?.lua" is a one-line difference. It's completely tangential to the criticism I gave.