On Friday, March 18, 2016 at 3:05:25 PM UTC-4, band...@mozilla.com wrote: > > This seems like a workable solution, as horrible as it is. One could > similarly make distro packages of rustc specifically for building firefox > (called 'rustc-fx' for example), and put them on the same ESR upgrade > schedule as Firefox.
Please no. It would be only a matter of time before firefox/mozilla would no longer be able to be built with a standard upstream rust package due to some sort of idiosyncracy in rust-fx. > > As another idea: Rust could maintain an LTS branch designed to be upgraded in > conjunction with Firefox, that both keeps the language on a stable revision > while also exposing backported features that Firefox needs in a controlled > way. So Firefox would commit to being on e.g. 1.12 for 3 years, but could > import 'future' features. Then LTS distros would put rustc LTS point releases > on the same upgrade schedule as Firefox ESR upgrades. Given that I know very little about rust, and putting aside the activities of Rust upstream's releases in general, what do we expect is going to be needed here in terms of a rust package to build an ESR vs a regular firefox release? I assume / hope that if firefox-52ESR can be built with say, rust-2.1 , that it can also be built with the rust-2.4 that's needed to build firefox-58 ?? If that isn't the case, ie, the version of rustc/libstd/etc that's installed can only build source that's compatible with that version of the rust language, then us distros will just need to keep around (and likely allow parallel installation of) all the different rust versions. Not ideal, but it isn't like this is anything we haven't had to deal with before. The main issue here will be with backporting rust code from mozilla-central to fix the ESR's, since its possible the newer code is going to need a newer rust language. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
