On Tue, Dec 21, 2010 at 2:15 PM, Alexander Gladysh <[email protected]> wrote: > Hi, list! > > I thought, I should collect all my "feature requests" in a single > place, so they would not get lost in the noise. > > Hisham, maybe LR needs an issue tracker? What if I use one on github?
Some people started using it already, so feel free to do so. I get emails when things are posted there. > -- No support for dependencies with "." in name > > LR Team position: fixed in 2.0.4 > > Solution: clench teeth and wait for a release > > > -- luarocks show (and maybe others) do not print errors to stderr. > > LR Team position: to be fixed in 2.0.5 > > Solution: clench teeth and use workarounds. The reason why I never worried about stdout vs. stderr is because the output of LuaRocks was never designed to be machine-processed. I can audit the code to find every occurrence of print and evaluate whether it should be changed to io.stderr:write (and patches are welcome in that regard), but that won't make the output of LuaRocks entirely predictable anyway, since it has various modes of operation depending on which external tools are used, and I never committed to keep the output identical from version to version, since it is designed for interactive users to read, not to be fed to scripts. > -- copy_directories copy lib/* directories to /usr/local/lib/lua/5.1/ > instead of rock directory > > LR Team position: this is a feature > > Solution: clench teeth and don't ever use lib/ directory. This is a side-effect of the combination of two features and under-specified behavior. > -- LuaRocks wraps any Lua script in bin/ without asking user > > LR Team position: this is a feature > > Solution: clench teeth and use workarounds. > > > -- Can't get a list of files that would be packed in a rocks for a rockspec > without building it > > LR Team position: impossible with the current codebase > > Solution: clench teeth and write my own code Why should you clench teeth on this? Was I expected to have written the code such as to make it easy to produce a manifest of rocks without building them without ever knowing that someone would need a feature? (Especially taking into account that one of the earliest LuaRocks requirements was to work with third-party build tools such as make, which render this task impossible anyway.) > -- LR can't build a rock without installing it into a system > > LR Team position: ??? > > Solution: clench teeth and use luarocks make That is exactly my position. I don't know what exactly you mean by that. I've received requests to change the behavior of luarocks make and split it into two commands, "luarocks make" and "luarocks make-install", but given your solution I don't think that's what you are asking for. If what you want is to be able to run "luarocks build" and get a .rock file without affecting any of your rocks trees, then I acknowledge the limitation. I consider this, however, to be a missing feature and not a bug. > -- LR does not allow user to specify a compression ratio when packing a rock > > LR Team position: wontfix, too specific > > Solution: clench teeth and waste CPU and developer time Or just clench your teeth and use a workaround: try environment variables such as GZIP and ZIPOPT, or even alias the compressor in your environment. > -- post_install hook is run before data is deployed to the rock directory > > LR Team position: bug confirmed > > Solution: clench teeth and do not use post_install until fixed > > > -- No pre_install hook (have a fix in Steve's repo) > > LR Team position: will consider after 2.0.4 > > Solution: clench teeth and wait > > > -- No support for ssh-based source protocols (like git+ssh), > since LR is to be run with sudo, and root does not see my keys > > LR Team position: wontfix, LR will not try to elevate privileges > > Solution: clench teet and install private code with luarocks make > > > -- No support for metadata in rockspecs. I need to be able to put > "x-something" fields anywhere in the tree. (Have a fix in Steve's repo.) > > LR Team position: will consider after 2.0.4 > > Solution: clench teeth and wait > > > -- luarocks make may be run only from the root directory with rock sources. > (Have a fix in Steve's repo.) > > LR Team position: will consider after 2.0.4 > > Solution: clench teeth and wait > > > -- No machine-friendly way to get a list of installed rocks. > (Have a fix in Steve's repo.) > > LR Team position: will consider after 2.0.4 > > Solution: clench teeth and wait > > > -- Each time when I ask if I can help somehow to get my feature requests done, > I get silence in answer. > > Solution: I need to see a stomatologist I'm not sure if I get the joke, but I'm sorry if my feedback is unhelpful. -- Hisham _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
