On Thu, Sep 9, 2010 at 5:28 AM, A.S. Bradbury <[email protected]> wrote: > On 8 September 2010 22:53, Alexander Gladysh <[email protected]> wrote: >> If I understand correctly, if I require GPL-ed module from my program, >> it becomes GPL-ed by itself. > > It's worth bearing in mind that this is only applies for > redistribution. Unless you redistribute you have no requirement to > comply with these terms of the GPL. This means for applications or > scripts meant for internal or personal use GPL-licensed libraries > aren't a problem. Some Lua developers may also be writing applications > they intend to release under the GPL, where again the license would > not bother them and the convenience of installing through luarocks > would be useful. > > I do quite like the idea of printing the license name upon install, > even if most developers would have checked the website to evaluate a > module (and presumable note the license there) before installing.
I'm against placing any restrictions on free software licenses for the public repository, but I added a message informing the license and installation directory in the 'build' and 'install' commands. That should suffice. http://github.com/keplerproject/luarocks/commit/455818ca4ce650a31a27de7f2a57c04293c2ffe8 -- Hisham _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
