I wanted to remember how to be a Debian Developer, and rust-1.0 is coming up, so I thought it was time to look into how one might package up rust for a distribution (yes, I'm aware a few other DDs have looked at this earlier; I've read some of their wiki pages/code but no, I haven't contacted them yet).
Once rust is bootstrapped on a new distro/architecture, it would be nice to be able to build a rust release using the regular rust compiler rather than downloading a pre-built opaque stage0 blob. How would this work in practice? Specifically, once we reach 1.0: - Will the rust stage1 source be limited to using "stable" rust language features? - What sort of version skew between stage0 and stage1 will be supported? Additionally, I currently see numerous "breaking" changes transitioned via #[cfg(stage0)]. The assumption is that stage0 is older than the breaking change, and stage1+ is newer than the change. Amongst other things, this means that you can't currently have the full compile-experience (using --enable-local-rust) using a compiler that you've just built :( I see there's already been discussion towards other mechanisms for tagging version-specific code(*). I'm new to the rust mailing list and community, so mostly I'm just looking to get caught up on the conversations around this and register a vote for "we need to have a story around this for 1.0, and not later". (*) http://discuss.rust-lang.org/t/pre-rfc-rust-version-attribute-specifying-rust-language-version-within-source-code - Gus
_______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
