On 25 September 2014 08:17, Gunnar Zötl <[email protected]> wrote: > Hi, > > I had an idea while fiddling with a project. In this project, some > decompression > libraries are used for building a lua library. However, depending on > circumstances, you may not want all of them. So I thought, would it be > reasonable for luarocks to have optional external dependencies, and command > line > flags to (de-)select them?
I'm planning to add an "add-on" system through which features like that can be loaded by rockspecs that need it. (I outlined my initial proposal for this at last week's workshop: http://www.lua.org/wshop14/Muhammad.pdf ) For this specific use case you mentioned, I'd personally try to go with a simpler solution, such as providing multiple rockspecs for different backend libraries. lrexlib does this: https://rocks.moonscript.org/search?q=lrexlib also, luasql: https://rocks.moonscript.org/search?q=luasql -- Hisham ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Luarocks-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/luarocks-developers
