On Fri, Mar 18, 2016 at 4:01 AM, Sylvestre Ledru <sle...@mozilla.com> wrote:
> Le 17/03/2016 à 21:30, Henri Sivonen a écrit : > > On Thu, Mar 17, 2016 at 2:28 PM, Sylvestre Ledru <sle...@mozilla.com> > wrote: > >> In Debian & Ubuntu, > > I didn't find a rustc package on http://packages.ubuntu.com/ . What's > > the situation on Ubuntu? > I thought it was already synced for xenial. I just filled the request: > https://bugs.launchpad.net/bugs/1559001 > > > >> we use the official binaries provided to be able to build rust. > > My same logic, can Mozilla-built rustc be used to build the Firefox > > package as far as policy matters, with exceptions and waivers taken > > into account, go? Or is this what's keeping rustc not getting past > > testing? > Debian stable will use the version of rustc at the time of the Debian > freeze (January 2017) > > > > > > On Thu, Mar 17, 2016 at 2:47 PM, Sylvestre Ledru <sle...@mozilla.com> > wrote: > >> One way which would make the life of Linux distro way easier would be > >> to maintain the Firefox rust code in a way it could compile using older > rust compiler. > > In order to be competitive, we need all leverage we can get from our > > Mozilla magic sauce (Rust). I think it's unacceptable to limit our > > ability to leverage Rust in Gecko by forgoing the ability to co-evolve > > Rust and Gecko at a rapid pace. > I understand your point, it is just conflicting with the goals of Debian > and Ubuntu LTS. > Mozilla wants to move fast, distros wants to provide stable products... > > > >> Now, with my Debian/Ubuntu hat, maintaining rust backports to be able > to build new versions of Firefox on stable/LTS releases > >> is not going to be easy > > Could Firefox in Debian stable have a build dependency on rustc from > > Debian unstable? > Nope, this doesn't work this way. Packages must be built in the env they > are going to be used. > Otherwise, it would lead to side effects (different version of libraries > used for build time and runtimes). > > One dirty solution would be to ship rustc+llvm sources into Firefox > sources when targeting stable distros. > But this increases the load on the maintainers by an order of magnitude > (maintainers will have to manage rust & llvm) > and might not work if llvm starts requiring a more recent of gcc to build. > However, this is really the last option distros will consider (and I am > sure Glandium will choke when he will read this). Related to this, Tor has deterministic and reproducible Firefox builds. They basically have a trusted base image providing GCC, glibc, binutils, etc then rebuild the world from source. When we introduce Rust, they will presumably need a way to build rustc from source without bootstrapping from pre-built binaries [that can't be trusted]. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
