[Pkg-rust-maintainers] Please consider packaging a Rust version that allows #![feature(...)]
gus at debian.org
Mon Aug 31 13:08:05 UTC 2015
On Mon, 31 Aug 2015 at 20:41 Ximin Luo <infinity0 at debian.org> wrote:
> On another note, I'm pretty sure we don't need to do the
> Conflicts/Replaces. Isn't the whole point of using a name like
> libstd-rust-xxxx is to be able to install two of them side-by-side?
Correct, different libstd-rust-xxx can be installed side-by-side just fine,
and the Conflicts/Replaces is unncessary. It was mistakenly added in the
last version, and we just haven't removed it yet.
> I've filed  to ask at least whether we can make it human-readable.
>  https://github.com/rust-lang/rust/issues/28120
To your point above, I don't think semver is a good fit here, since the ABI
in the library is completely incompatible between rustc versions. There is
no implicit order, and "minor" increments in rustc do _not_ produce
forwards compatible libstd-rust-xxx libraries. (The Rust-level API has
compatibility guarantees, but the dylib ABI does not)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-rust-maintainers