2010/10/10 steve donovan <[email protected]>: > On Sat, Oct 9, 2010 at 10:57 PM, Jerome Vuarand > <[email protected]> wrote: >> I've finally taken some time to write rockspecs for Lunary. I attached >> them to this email. Since these are the first one I publish tell me if >> anything is wrong with them. For more information about the library >> itself you can check the following website : > > All worked fine here on Debian, if of course installed in the correct > order. I appreciated the well-organized web site and manual, since > these are so often 'after thoughts'. It might however be an idea to > distribute some of the examples in a 'sample' or 'tests' directory > (i.e. use build.copy_directories) since often my first urge is to go > and run some code. > > (luarocks show does make it easier to find the correct directory)
The examples are easily accessible on the web page and in source tarballs. I'm not very comfortable with installing scripts on the user computer that he doesn't expect, and AFAICT there is no way to opt out of these copy_directories. But if that's the norm in rocks I'll add my examples. Will there ever be a specific field in the rockspecs so that users could tree-wide decide whether to install examples or not ? > As a consequence of the module organization, 'show lunary' does not > show the modules, but 'show lunary-core' does. That's a serious drawback, I've got to think about it. > A comment about a > module name 'serial' is that it may be over-generic, and might be > confused with a serial communications library. > > I don't know what others think, but 'lunary.serial', etc? This is a > pedantic point; everything otherwise went smoothly. There are two reasons for that. First the module existed before the "Lunary" name. Second I took inspiration from other rocks, like LuaBitOp, which uses the "generic" bit namespace, or luaposix and lposix which both use the posix namespace. For these reasons I'd rather not change the module name, but I guess that's your call. _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
