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

Luca Bruno lucab at debian.org
Mon Aug 31 09:59:48 UTC 2015

[Also moving this part of the thread out BTS, back to ML]

On Monday 31 August 2015 11:26:13 Ximin Luo wrote:

> So this actually contains no extra information than the strings (e.g.)
> "1.3.0" or "1.3.0-beta.3" or "1.3.0-nightly" etc, but has the disadvantage
> of not being comparable. I am wondering if we should just (a) patch this to
> use $(CFG_RELEASE) instead, and maybe (b) call the package libstd-rust-1,
> since semantic versioning is supposed to mean backwards compatibility
> between 1.3.0 and 1.2.0. That would be more sane, and I've asked in #rust
> about it.

We are talking here about the SONAME of rustc-provided shared objects (.so) 
here, and the idea is that package name match the libraries' suffix.

Given that rust doesn't have a stable ABI, I'm pretty sure that talking about 
semver stability doesn't apply here (but I haven't checked the symbols).

Moreover, this hash suffix is deeply rooted into rust/cargo dylib generation, 
so I would avoid patching stuff on our side.

Cheers, Luca

 .''`.  ** Debian GNU/Linux **  | Luca Bruno (kaeso)
: :'  :   The Universal O.S.    | lucab (AT) debian.org
`. `'`                          | GPG: 0xBB1A3A854F3BBEBF
  `-     http://www.debian.org 	| Debian GNU/Linux Developer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-rust-maintainers/attachments/20150831/3ab43fef/attachment.sig>

More information about the Pkg-rust-maintainers mailing list