NoisyCoil authored 9 months ago and Pier Angelo Vendrame committed 8 months ago

Our binaries are already stripped, so avoid stripping them again when
creating Debian packages, as the version of binutils in our containers
cannot understand some ELF sections of the new binaries generated after
the Firefox+toolchain update.

Our build servers cannot reach maven.mozilla.org through IPv6.

With this commit, we switch to requests (we have it anyway, since we
use it to build changelogs), which downloads dependencies on memory
first, but usually dependencies are small and you need a giant amount
of memory to build Java stuff anyway.

Now the APKs are produced in the GeckoView project, rather than
firefox-android.

The steps to build Fenix after the migration to the monorepo are very
similar to the ones we used to build it from the previous repository.
However, they need to be run on the tor-browser.git repository, so in
this commit we move part of the firefox-android project to the
merge_aars phase of GeckoView.

Google dropped support for KitKat in the Play Store.
So, the minimum API level supported by the NDK and by Firefox is 21.

In the android-toolchain project we used to add many versions of the
tools we do not actually need.
Also, since we are not building anything, but just extracting archives,
we can run the build outside containers.

This involves replacing all references to OpenJDK 11 with OpenJDK 17.

Updated the tools from Firefox 128.

Mozilla moved the YAML files in which they define their toolchain.
Also, updated how we check Rust's version.

configure_opt has been renamed to target_flags to avoid confusion with
the the flags usually passed to configure scripts generated from
autoconf.

Mozilla uplifted Bug 1900421 to 115 to 128, so we have to switch to the
new GitHub repository immediately as well.

Following @ruihildt's suggestions we update the desktop file:

- Added MimeType field (to have the browser listed as a possible default
  browser application)

- Removed `X-MullvadBrowser-ExecShell` which is not used

- Removed the "Security" category

- Added the Version (of the desktop entry specification we use)

- Added Terminal

After #41167, the portable Windows installer are not
generated anymore for Mullvad Browser. We should include the normal
installer (without `-portable-` or `-install-` in the filename) in
the download-*.json files.

And remove the `-install` from the other one.

This should make sure the script always bumps the build number in
rbm.conf if needed.