> Hisham, maybe LR needs an issue tracker? What if I use one on github? I second that. Github's tracker is crude, but at least the issues don't get lost and you can comment on topic.
> -- 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. Isn't that where C modules are placed? What's wrong with it? AFAIU it's a feature as you can point package.cpath to it and forget how the modules got there (i.e. don't have to load luarocks.require). > -- 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.) I thought you can put anything in rockspecs. If not, I need that too. > -- Each time when I ask if I can help somehow to get my feature requests done, > I get silence in answer. I'm sure that if you fork the repo, do your fixes and then push it back then your changes will be accepted if they make sense. The tracker comes in handy here so you can avoid duplicate effort. Basic open development stuff I guess :) PS: Your use case for compression options intrigue me -- last time I used it I had a 486 :) _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
