it shows in rustc -Vv rustc 1.28.0-dev binary: rustc commit-hash: unknown commit-date: unknown host: x86_64-unknown-linux-gnu release: 1.28.0-dev LLVM version: 6.0 for rust-bin: rustc -Vv rustc 1.26.2 (594fb253c 2018-06-01) binary: rustc commit-hash: 594fb253c2b02b320c728391a425d028e6dc7a09 commit-date: 2018-06-01 host: x86_64-unknown-linux-gnu release: 1.26.2 LLVM version: 6.0 this is not a cosmetic issue, because some rust features are activated only for -dev releases, which could break things.
Like what features? I did notice this and looked into it a little, but as far as I could tell it was just cosmetic, so would be interested in information to the contrary.
Ok, upon close re-reading I think I made a misstake here. There are unstable features available for -nightly tagged rustc binaries, but this doesn't seem to be the case for -dev tagged rustc binaries. The musl ebuild provides a regularly tagged rustc binary, you maybe want to have a quick look into it?
What musl ebuild do you mean? I'm not even sure if we should have our custom builds of rust masquerade as "official" release builds -- in the end, they're not blessed by upstream.
I agree, you're having a point here. Closing.
