wget version
jbenet opened this issue · comments
using system wget may be a problem:
wget: unrecognised option '--show-progress'
Usage: wget [OPTION]... [URL]...
Try `wget --help' for more options.
I have
> wget --version
GNU Wget 1.15 built on linux-gnu.
[snip]
for this reason, i tend to prefer not depending on system utils, and instead prefer to install own versions of tools. I really want to start making small tools that depend on ipfs being there to load their own dependencies. for example, if there is a portable wget we know about in IPFS can just depend on it and installing the tool is guaranteed to get us exactly that version. there's still portability concerns, but less. (this is some food for thought for us -- cc @whyrusleeping)
Hm, yeah, I'm using latest wget, which I think is wget 1.16.3.
If anyone know about a portable wget, would be great to learn about it so
please share.
Probably I'll rewrite this is a proper language in the future, bash is
neither nice to program in or portable. Once I do that, there wouldn't be
any system dependencies.
On Sun, Nov 8, 2015, 02:57 Juan Benet notifications@github.com wrote:
using system wget may be a problem:
wget: unrecognised option '--show-progress'
Usage: wget [OPTION]... [URL]...Try `wget --help' for more options.
I have
wget --version
GNU Wget 1.15 built on linux-gnu.
[snip]for this reason, i tend to prefer not depending on system utils, and
instead prefer to install own versions of tools. I really want to start
making small tools that depend on ipfs being there to load their own
dependencies. for example, if there is a portable wget we know about in
IPFS can just depend on it and installing the tool is guaranteed to get us
exactly that version. there's still portability concerns, but less. (this
is some food for thought for us -- cc @whyrusleeping
https://github.com/whyrusleeping)—
Reply to this email directly or view it on GitHub
#5.
any fix for this yet?
On ubuntu you can use this wget: https://launchpad.net/ubuntu/+source/wget/1.17.1-1ubuntu1/+build/8819663
still having the above problem but on OSX since it had an earlier version of wget as well. but I used homebrew to get a more recent version. I had to update to explicitly use a different path.