61–70 of 176 posts
Is there really a point these days in having the very last release rather than the ESR version packaged by Debian? If so what are the benefits for end users?
Most companies don't prioritize legacy support, so there is no point in developing for Firefox ESR.
They don't seem to be packaging the LTS version, Firefox ESR. Am I missing something? Is there a separate Mozilla repository for that?
This way, I get the official Firefox package without Mint adding their own stuff on top of it, I get the official Firefox icon and not Mint's icon theme variation of it, I don't need to edit keyring files or import GPG keys, and it updates automatically without forcing me to restart the browser.
[1] https://github.com/sandov/sc/blob/master/install_scripts/fir...
Takes 7 steps to install Firefox this way as opposed to apt-get install.
> Getting the latest version with features and security fixes is key to having a good experience whenever you use Firefox. Now, our new APT repository is directly connected to the Firefox release process, so you will receive the latest updates whenever we make them available. Tip: you will still need to restart Firefox for the latest version. In the past when I've installed Firefox through a .deb, it has had this ann…
Is there really a point these days in having the very last release rather than the ESR version packaged by Debian? If so what are the benefits for end users?
Is there really a point these days in having the very last release rather than the ESR version packaged by Debian? If so what are the benefits for end users?
I personally don't see a good reason to opt out of security changes for any longer than strictly necessary and that's exactly what you do when using ESR. First they get backported by Mozilla. That's after normal users receive them. This takes time. Then testing takes place because they don't want to push out a hasty fix for ESR. This takes more time. And then third party packagers need to pick up the changes and repackage (which is mostly pointless and adds more time). And then eventually it rolls out days/weeks/months after normal users have long received the patches. I don't seen any good reason for such lengthy delays for normal users. In some big companies where they manually review updates for workstations it's a compromise between the extra work and stability. But the tradeoff is timely access to security fixes; which ESR simply doesn't provide.
This is a welcome addition for Chromebooks, because now you can install latest Firefox (not ESR) in Crostini without using Flatpak. Sadly Mozilla still doesn't offer `aarch64-linux` builds for Firefox in their official channels, so for those that have a ARM64 Chromebook will still need to use something else to get Firefox running (I use Nix, but it needs some complicated setup to work with hardware acceleration, for…
Hey, do you know a good resource to learn how to compile a binary for Linux Arm64 that works in a Chromebook? I would like to port some C code I have that I produce builds for x86 and Amd64 debian using GCC 4.8 and an old debian, I am curious what has to be done to produce a binary that would run the same in Chromebook.
So just target Debian 11 and 12 arm64. If you compile on an older version of Debian it should work fine too.