[Pkg-rust-maintainers] rustc/cargo in stretch

[Matthias Klose]

On 03.05.2017 17:04, Luca BRUNO wrote:
> On Wednesday, May 3, 2017 12:09:11 PM UTC Julien Cristau wrote:
> 
>>> So I think we should remove both packages from stretch and avoid painting
>>> ourselves into a corner.  Thoughts?
> 
> Can you elaborate a bit more on the "paint ourself in a corner"?
> 
> From my side, I can contribute these datapoints:
> * there are no rdeps on purpose, as we decided to postpone policy + dh-cargo +   
>   libs/apps after stretch release
> * rustc and cargo are now tied in self-bootstrapping and crossed-bootstrapping
>   loops, so having at least some (albeit old) versions of both in a release 
>   may help

it doesn't, because you always need the immediate predecessor version for a
bootstrap.

> * those packages are mostly intended as stepstones to a full ecosystems of 
>   libs/apps and to make backports slightly easier, users are basically 
>   expected to use rustup anyway (as the language is still evolving)
> * firefox security updates story is more complex than I currently grok,
>   but it may involve shipping a fresh cargo+rustc+llvm toolchain either ways

it comes down to how you want to support firefox. If you want to have it updated
in stretch itself, then you should ship (and update) that toolchain in stretch
as well.

Matthias