Now that rustc is required for firefox, I would like to suggest that we do not automatically update it on each new release. I have noted in the book that newer versions of firefox will probably need newer versions of rust, but I am now suggesting that this should be proven for each new firefox release.
For firefox, there is a release calendar to suggest when new versions will appear, at https://wiki.mozilla.org/RapidRelease/Calendar - FF53 is still in the 'Future branch dates' table at the top, read _down_ that table. So ff54 is expected in mid-June (occasionally the releases slip). For rust and cargo the releases are nominally every 6 weeks, the last was on 16th March so I suppose the next will be around this Wednesday. Mostly we drop the latest versions in all the time, except when we defer updating because of too frequent releases. But arguably at least kde is in a similar situation - they release frequently, we don't pick up each new version. Because rustc is only used by cargo and firefox, and cargo only by firefox, and also because on a non-workstation machine it is such a heavy build (slightly slower even than firefox) I think we should care for our users and not imply they should upgrade if the current version will actually be good enough. For firefox-54 I will not attempt to build a beta until a new beta has been released after the next rust and cargo. By the time a later ff54 beta comes out, it may well be that newer cargo and/or firefox are indeed required - but if we can save users from unnecessary rebuilds then I think we should do so! With such an approach, I hope that at least some of the next firefox releases will not force people to rebuild rust. ĸen -- Error: ( : 1) not enough arguments Don't you just love Tiny scheme ? -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
