On May 7, 2013, at 3:58 AM, Philipp Janda <siffie...@gmx.net> wrote: > For the dependency issue I hope that we can find something faster …
Yes. If there is evidence that a rockspec is inaccurate, e.g., if the dependency information is wrong, then the rock repository maintainers should have the authority to fix it or remove it from the repository. Notifying the developer or rockspec maintainer, and giving some time for the developer/maintainer to make a repair would be nice. If the repository accumulates broken rockspecs its value diminishes. Surely those who put time into managing the rock repository should not be forced into a situation where the repository is unreliable because the rockspecs are inaccurate. This is exactly why I proposed no longer accepting open ended dependencies such as "lua >= 5.1" -- over time this is virtually guaranteed to result in broken rockspecs. There is no justification for asserting that a rock is compatible with Lua 5.3. e ------------------------------------------------------------------------------ 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
