Comment # 12 on bug 1112817 from
(In reply to Frank Kruger from comment #11)
> (In reply to Luke Jones from comment #9)
> > > Was rust and cargo in the past switching version in the same pace. So rust 1.26 > and cargo 0.27 or something?
> > >
> > > In any case the Firefox configure check expects this:
> > > 
> > >     rustc_min_version = Version('1.28.0')
> > >     cargo_min_version = rustc_min_version
> > > 
> > > So I expect we need cargo 1.28 at least as well.
> > 
> > This is correct. The Rust spec now builds all included tools [cargo,
> > rustfmt, rls, clippy, analysis]. Cargo should have the version changed to
> > 1.30.0, so maybe if you set the minimum version to that for cargo it could
> > help?
> > 
> > ** Just checked, I think we need to delete existing cargo from all releases
> > to resolve this. I'm unsure what else I can do to help the situation.
> > 
> > Is there something like an: Obsoletes: cargo <= 0.28? Would that work?
> > 
> > It's been tough getting this sorted as it takes 6-12 hours to build Rust on
> > the available hardware.
> 
> I appreciate your efforts! Do you expect any improvements regarding build
> time in the future? Thx.

No, not unless it builds on better hardware. More cores doesn't really improve
speed that much, above 4 cores gives rapidly diminishing returns.
It's the nature of Rust unfortunately, but it will improve over time from
upstream efforts.


You are receiving this mail because: