Hi all, It's time for that discussion again!
- Naturally a new format would be versioned, and be a superset of the existing format to cause minimal disruption. - There is a need to beef up the detection of external dependencies. The rockspec for Gunar Zoetl's ltcltk contains comments, and is a poignant little essay in itself. http://www.luarocks.org/repositories/rocks/ltcltk-0.9-2.rockspec Basically, no one agrees where to put tcl headers. The cases he covers are /usr/include, /usr/include/tk which he discriminates using per-platform overrides. But on Debian it's /usr/include/tcl8.4 or /usr/include/tcl8.5 So we'd need something like this: external_dependencies = { TCL = { header = {"tcl.h","tk/tcl.h","tcl8.4/tcl.h","tcl8.5/tcl.h}, library = {'tcl8.4', 'tcl8.5'} } } with the understanding that all possibiites are checked. This would really improve the capabilities of the builtin build mode. Then it would be easier to persuade people not to bundle makefiles and actually use LuaRocks as a build system. - this point may feel trivial in comparison, but having 'author' as well as 'maintainer' makes the roles distinct. I think this would encourage a separate group of 'packagers' who could then package other people's projects without seemng to imply that they are indeed the Author. steve d. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
