On Mon, Sep 10, 2012 at 5:11 AM, Jack Lawson <ajacksif...@gmail.com> wrote: >> a "no-downloads-at-build-time" policy > > which are occasionally necessary when one needs to, for example, download > libraries conditional to a particular environment unknown beforehand. It > seems that, if you have a policy restricting these kinds of libraries, you > should either look hard at why that's an absolute policy or find another > library to use.
What I meant by "no-downloads-at-build-time" is that all source code used to build a rock (excluding external dependencies and dependencies on other rocks) should be stored inside a .src.rock file. If a rock depends on a library or on another rock, it should specify so in either its "dependencies" or "external_dependencies" tables (optionally set conditionally with the "platforms" directives). The idea is that the rock should continue to work if we have a .src.rock in the main repo and the upstream site goes down. -- Hisham ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
