It was thus said that the Great Hisham Muhammad once stated: > On Sat, 15 Sep 2018 at 22:28, Sean Conner <s...@conman.org> wrote: > That is odd, curl --version returns exit code 2? On my machine running > curl 7.53.1, I get a 0: > > hisham@proxy ~]curl --version > curl 7.53.1 (x86_64-pc-linux-gnu) libcurl/7.53.1 OpenSSL/1.x.x zlib/1.2.8 > Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps > pop3 pop3s rtsp smb smbs smtp smtps telnet tftp > Features: IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz > TLS-SRP UnixSockets HTTPS-proxy > hisham@proxy ~]echo $? > 0 > > I'm guessing I could anything other than a 127 to be a success, as in > "the program does exist". Would it be possible for you to upgrade curl > so we could confirm that it's a version issue?
I did a test on a newer machine (my system at work) and yes, "curl --version" returns 0. So this looks like it's a curl version issue on my end. > > Yes, I am running a rather older system, but it hasn't been much of an > > issue. > > Indeed, curl detection (which is needed by `luarocks upload` when > LuaSocket isn't installed) used to happen at configure-time > scanning for $PATH, and now it shifted to probing the command at runtime. How do you do the detection? Is it just through os.execute() or do you actually check each directory in $PATH for curl? If you search $PATH for curl and it exists and is executable, then does it matter what "curl --version" returns? But it's nice to know about LuaSocket. I think I had that installed so I can try that approach. -spc _______________________________________________ Luarocks-developers mailing list Luarocks-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/luarocks-developers
