I think you are trying to compile a project that requires in-development features of the Rust compiler. I think you also want to do that without getting involved in the Rust upstream development process and tools (like rustup). I don't think there is a way to resolve those two conflicting goals to anyone's satisfaction.
I think the long-term solution for your project is to move to using only stable Rust features (which would then be supported by the rustc Debian packages). (The current Debian/Rust choice is to only package stable toolchain releases, as we see that as our role (as a distro) within the Rust ecosystem. If you want to develop rustc itself, or work with unreleased/unstable features, then you will need to be prepared to join the Rust community and their recommended tools (probably rustup, not apt-get).) - Gus On Fri, 26 Jul 2019 at 05:09, Dmitry Bogatov <kact...@debian.org> wrote: > > Source: rustc > Severity: wishlist > > Dear Maintainer, > > are there any plans to add into Debian version of Rust compiler, that > supports #![feature]? > > Currently, to compile project I am interested in, I am forced to use > `curl | sh` installation, which is quite creepy. > > -- System Information: > Debian Release: bullseye/sid > APT prefers buildd-unstable > APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500, > 'testing'), (1, 'buildd-experimental'), (1, 'experimental') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) > Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL > set to en_US.utf8), LANGUAGE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set > to en_US.utf8) > Shell: /bin/sh linked to /usr/bin/dash > Init: runit (via /run/runit.stopit) > LSM: AppArmor: enabled > _______________________________________________ > Pkg-rust-maintainers mailing list > pkg-rust-maintain...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-rust-maintainers > -- - Gus