5 ms·
>"When it comes to Linux things work differently than on other platforms: most of our users do not install our builds, they install the Firefox version that com
by Barrin92 5y ago
>"When it comes to Linux things work differently than on other platforms: most of our users do not install our builds, they install the Firefox version that comes packaged for their favourite distribution.
This posed a significant problem when dealing with stability issues on Linux: for the majority of our crash reports, we couldn’t produce high-quality stack traces because we didn’t have the required symbol information. The Firefox builds that submitted the reports weren’t done by us. To make matters worse, Firefox depends on a number of third-party packages (such as GTK, Mesa, FFmpeg, SQLite, etc.). We wouldn’t get good stack traces if a crash occurred in one of these packages instead of Firefox itself because we didn’t have symbols for them either.
To address this issue, we started scraping debug information for Firefox builds and their dependencies from the package repositories of multiple distributions: Arch, Debian, Fedora, OpenSUSE and Ubuntu. Since every distribution does things a little bit differently, we had to write distro-specific scripts that would go through the list of packages in their repositories and find the associated debug information"
This is why I'm glad that a lot of Linux software is moving towards distro agnostic containerized applications maintained by developers. Linux already does not have a large market share and if you have to deal with a dozen distro-specific quirks it seems hardly economical.
- timbit42 5y agoSnap, Flatpak and AppImage all suck! Fix this first.
- deleted 5y ago[deleted]
- AnIdiotOnTheNet 5y agoUnfortunately they are solutions designed for a platform and ecosystem with a lot of suck built-in. For my money, AppImage has the most sane approach, but without support from the wider community they are still a bit of a pain.
- bogwog 5y agoI don't know what you're talking about, AppImage is great!
- e3bc54b2 5y agoAppImage is very good, I agree, but it has its fallings too. It also has external runtime dependencies that make it a pain to package and use on NixOS.
- Avamander 5y agoIt's awful. It's a pain to keep up-to-date, pain to keep track of the software's data, pain to force to adhere to conventions, pain to theme, it's absolute dogshite.
- _jal 5y ago> This is why I'm glad that a lot of Linux software is moving towards distro agnostic containerized applications To me, it entirely depends on the specific packaging job, not even who is doing it. Entirely too often, they ignore distro convention, and can introduce bugs and other security issues through ignorance, laziness or mistake. Long term, flatpack and its ilk will devalue distro differences and put pressure on uniformity. Whether or not you consider this is a good thing may depend on your opinion of/relationship to RedHat/IBM. For me, if it isn't in the Debian repos, I'm probably going to ignore it.
- _-david-_ 5y ago> Entirely too often, they ignore distro convention Can you clarify what you mean by this? I have used both the flatpak and rpm (on Fedora) version of Firefox and don't really notice a difference. Perhaps Firefox is just one of the packages that does distro convention properly?
- _jal 5y agoWasn't specifically referring to Firefox, didn't intend to imply that - I have not even used the flatpak version. It was a general comment that is not specific to Flatpak - it will a problem for any cross-distro packaging. (Heck, plenty of developers mess up native packaging for distros they're not familiar with.)
- diegocg 5y agoThis will stop being a problem when/if all distros start using symbol servers
- deckard1 5y agoI'm not holding my breath. The Linux Standard Base is 20 years old now. That was supposed to get us there. If Canonical and Red Hat cared, they'd probably go through the Linux Foundation instead of creating competitors to AppImage. Speaking of, AppImage is from 2004. So... see you guys in 20 more years.