[Pkg-rust-maintainers] Please consider packaging a Rust version that allows #![feature(...)]

[Angus Lees]

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 [1] to ask at least whether we can make it human-readable.

> [1] 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)

 - Gus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/attachments/20150831/d32be440/attachment.html>