On Mon, Sep 20, 2010 at 12:51 PM, Hisham <[email protected]> wrote: > On Sat, Sep 18, 2010 at 9:02 PM, Cosmin Apreutesei > <[email protected]> wrote: >> your test works on my machine (xp sp3)... btw, why not bundle luarocks >> for windows with working stock wget binaries? > > The Wget FAQ page points to three different locations to get wget > binaries for Windows: > > http://wget.addictivecode.org/FrequentlyAskedQuestions#Where_can_I_download_Wget.3F > > Which one should we bundle?
I haven't kept that up-to-date on recent LuaRocks/LuaDist developments, but I had been involved in earlier discussions concerning bundling external tools, like patch. First, why is wget needed? For the most part, luasockets is sufficient to download files. It's the only thing LuaDist uses for non-development work (i.e. excluding svn/git/hg). If you need https URLs, there is also LuaSec/openssl, which at one time I had created a CMake build for which built even on native Windows. wget is an a way a "complex tool" compared to luasockets, and one of its foci is recursive web crawling, which I don't think we need. It also introduces GPL licensing concerns, and IIRC I had trouble building it out-of-the-box on native (i.e. non-Cygwin) Windows. Another alternative is curl [1], which is MIT licensed, includes autoconf, CMake, and MSVC builds, and seems better supported on non-POSIX platforms (in fact, the portable build tool CMake itself links to libcurl). See here [2] for a comparison of wget and curl/libcurl. You can also link it as a library, and there apparently are two Lua bindings for that too [3]. [1] http://curl.haxx.se/docs/ [2] http://daniel.haxx.se/docs/curl-vs-wget.html [3] http://curl.haxx.se/libcurl/lua/ _______________________________________________ Luarocks-developers mailing list [email protected] http://lists.luaforge.net/cgi-bin/mailman/listinfo/luarocks-developers
