Open h1z1 opened 5 years ago
Which Rust version do you use?
Tried building 45523d81b0e08bda277616d80fff3b85e46c9f5c with rustc 1.34.0-nightly (f6fac4225 2019-02-03)
on GNU/Linux and I don't see the error.
Also builds after cargo update
. Also builds with rustc 1.31.1 (b6c32da9b 2018-12-18)
and rustc 1.32.0 (9fda7c223 2019-01-16)
, and rustc 1.30.1 (1433507eb 2018-11-07)
, with or without cargo update
.
@vi rustc 1.28.0 (9634041f0 2018-07-30)
You should either update Rust or use Websocat version tagged as "last_version_that_supports_rust_1_28". Currently you'll probably only miss the At the moment this tag should support all features present in master branch.--conncap
option compared to Websocat from master.
I noticed that README states 1.28 as a supported version. I updated this stale information.
Indeed. Was 45523d81b0e08bda277616d80fff3b85e46c9f5c meant to detect that?
This commit makes Travis check against 1.30 instead of 1.28. Also update dependencies that stopped supporting 1.28.
I want websocat to be eventually included in Debian repository, and outdated dependencies are not a good idea there. Rust version in Debian Testing is currently 1.31, so there's no real reason to support earlier Rust versions.
so there's no real reason to support earlier Rust versions.
Except every other distro / install that doesn't run nor track debian releases. You're of course free to do as you wish, just noticed it didn't compile.
Do you know any distros that are locked to older Rust versions? Debian is not a fast-paced distro and I expect it to have older Rust compared to a typical other distribution (except of Red Hat / CentOS world)
If there are specific examples of distributions that accept Rust-based packages into repositories and that are expected to still be containing Rust 1.28 half a year in future (for example), I may consider keeping a 1.28-compatible branch and backport fixes there if possible.
Coming from CentOS/RHEL, I wouldn't expect much in at least official repos if that is what you mean? There are community backed ones of course. Rust 1.31 is in EPEL. 1.29 isn't that old as far as api breaking deprecation goes but TBH I don't use Rust enough to care either way. Wrote a wrapper in bash.
Websocat 1.2.0 should be OK for current CentOS/RHEL then (I can try to make a pre-built RPM in Github releases if needed).
But Websocat 1.3.0 would probably require later Rust version.
Fully admit I don't know a lot of Rust so not sure what is wrong. From what I gather quote fails to compile? 45523d81b0e08bda277616d80fff3b85e46c9f5c tries to bump the minimum rust version but I didn't receive any such error.