Am 07.05.2013 18:05 schröbte Jack Lawson: > Or you could just fork the code and upload a new version of the rock and > use and promote that,
New name or old name? If new name, you basically get *more* unmaintained rocks in the repository (see lposix vs. luaposix). You would also have to change/fix/fork all rocks having this one as a dependency ... > instead of changing someone else's code, and then you I proposed changing (fixing) someone else's rockspec, not their code ... > can avoid this whole mess. If the owner isn't updating an older rock, by > virtue of entropy (and perhaps statistics on how popular a rock has been > the last month) the new one will take over. Like with luasocket, for example?! Fortunately, luasocket specifies correct Lua dependencies ... Philipp ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. This 200-page book is written by three acclaimed leaders in the field. The early access version is available now. Download your free book today! http://p.sf.net/sfu/neotech_d2d_may _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
