Regardless of our future plans for the default browser, it would be good to be able to get the current stable Firefox on PureOS from the repos (currently we only have ESR).
Even if we shipped Epiphany by default, a lot of people would still install Firefox, and expect to get the stable release (currently 65, while ESR is 60).
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T366 PureOS is too stable including packages only from Debian testing | ||
| Restricted Maniphest Task | ||||
| Wontfix | None | T689 PureOS lack a more frequently updated Firefox (regardless of branding, and regardless of which is default) |
For clarity, you mean adding a stable Firefox with its own branding and without any changes to defaults, right? This shouldn't be an issue since PureBrowser would be the default and Firefox would require installation by the user.
Well, as we discussed in https://tracker.pureos.net/T688, we want to get rid of the PureBrowser branding anyway.
I think given our privacy focus, keeping our very minimal changes to Firefox could still be nice (afaik it's mostly uBlock Origin being installed and Duckduckgo being the default search engine), but I'm not sure what other implications that would have.
@jeremiah.foster: No, this ticket is explicitly about the functionality, not branding of it!
I find that expressing tickets as what is wrong helps.
@tbernard do my current rewrite of title correctly reflect your intent for this ticket?
@jonas.smedegaard sure, the new title makes sense to me.
Basically, people expect to have the current stable Firefox release available in the repos, because that's what most distros have (and what they'd install on other platforms).
Tracking fast-changing packages in particular need strong monitoring e.g. by somthing like security-tracker.debian.org.
Users also have the option to install "unofficial" flatpak'd Firefox here if they feel comfortable with the possible lack of security: https://firefox-flatpak.mojefedora.cz/
@jeremiah.foster please elaborate on your title change - is this issue not about _continuously_ updating at a faster _pace_ but only about getting some specific new version?!?