Context Navigation

Changes between Version 99 and Version 100 of firefox

Timestamp:: 08/15/2021 06:59:52 PM (3 years ago)
Author:: ken@…
Comment:: Start to clean up older information

Legend:

: Unmodified
: Added
: Removed
: Modified

firefox

-              v99
+              v100
 = Firefox =
 == Profiles ==
 …
 == Which version should I use ? ==
 In general, BLFS tries to always use latest releases. For firefox up to and including 69.0 the latest version has normally been used. But in late 2019 mozilla decided to move to a more-frequent release schedule (eventually 4 weeks instead of 6 or 7 weeks).
+In general, BLFS tries to always use latest releases. For firefox up to and including 69.0 the latest version was normally used. But in late 2019 mozilla decided to move to a more-frequent release schedule (eventually 4 weeks instead of 6 or 7 weeks).
 Newer versions tend to need newer versions of rust, but this can cause problems with other packages which use rust. In particular, thunderbird releases are based on the firefox esr (extended support releases) code and tend to have code which does not build with the latest version of rust.
+Newer versions tended to need newer versions of rust, but this can cause problems with other packages which use rust. In particular, thunderbird releases are based on the firefox esr (extended support releases) code and tended to have code which did not build with the latest version of rust. Nowadays, seamonkey is also in that situation.
 There are only a few packages in BLFS which use rust and the editors aim to ensure that all the versions in the book can be built with the same version of rust.
 As a result, after firefox-69 the book has moved to the esr versions of firefox which for 68esr was technically a downgrade ''(see details about profiles above)'', but contain all the relevant security fixes.
+As a result, after firefox-69 the book moved to the esr versions of firefox which for 68esr was technically a downgrade ''(see details about profiles above)'', but contained all the relevant security fixes.
 '''You should always use the latest release, either the latest esr or the latest mainline version (or the latest beta for bleeding edge)'''. And you should remember to update your ca-certificates when building a new version of firefox.
 …
 The minimum rustc version remains at 1.41.0, which was buggy. But you should upgrade rust to rustc-1.52.0 to fix various vulnerabilities and versions less than 1.52.0 will no longer be used for testing. If your version of llvm is less than 9.1, build rustc using its shipped llvm (see [http://wiki.linuxfromscratch.org/blfs/wiki/rust]).
-== Other changes to the build between 68esr and 78esr ==
-The patch for system graphite2 and harfbuzz has been discontinued. Shipped graphite2 was changed by mozilla so that the patch did not build. Later it became clear that with a revised harfbuzz patch the shipped harfbuzz code was still being compiled.
-System sqlite can no-longer be used. Many years ago, having the shipped sqlite in the browser but with system sqlite used by other packages was reported to cause problems. So far, things now seem ok.
-''Importantly, after ff70 ./mach install no longer accepts '--verbose' and errors if it is used.''
-A profile which was created for 73.0 seems to work ok.
-The available configure options have changed dramatically in 78.0, please review the up to date mozconfig in the book.
 == Changes to the build since 78.0 ==
 …
 }}}
 I do not want to try the system python option because that looks as if it will use pip to download required packages and perhaps try to install them on the system.
+I did not want to try the system python option because that looks as if it will use pip to download required packages and perhaps try to install them on the system.
 Using './mach create-mach-environment' before running other mach commands (but after the exports) works.
+With 78.7.0 I have changed the './mach build' invocation to first run './mach configure' (just checking deps and creating the build files ("reticulating splines") to be more consistent with conventional packages, followed by './mach build' after noticing this in an AUR thunderbird build.
+In firefox-89 the UI has been changed. That has met with mixed reactions.
+Note that gcc-11.1.0 as released cannot build 89.0, gcc-10 was ok, as is clang-12.0.
+That has now been fixed upstream at gcc for gcc-11.2.0 and later [https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100644] patch is currently at [https://www.linuxfromscratch.org/~ken/test/] pending further testing. Obviously you need to rebuild gcc to use this.
+From 78.7.0 I changed the './mach build' invocation to first run './mach configure' (just checking deps and creating the build files ("reticulating splines") to be more consistent with conventional packages, followed by './mach build' after noticing this in an AUR thunderbird build. For those of us who do not have rust on their normal PATH, or have multiple versions of rust, this allows a quick check that all is ok rather than running './mach build', leaving it and coming back to find it failed during the configure.
 == Withdrawal of ftp ==
 Not a change to the build process, but in 90.0 the ability to use ftp links was removed.
 If this bothers you, consider using firefox-legacy (currently 78.13.0) as a short-term workaround until you find an alternative.
+If this bothers you, consider using firefox-legacy (currently 78.13.0) as a short-term workaround until you find an alternative (current seamonkey and falkon permit this, but seamonkey tends to lag behind the firefox vulnerability fixes, while seamonkey requires qtwebengine which is a heavy overhead).
 == Problems with 91.0 failing to build ==
 …
 == Dependencies for 92.0beta ==