Closed Bug 1351723 Opened 7 years ago Closed 6 years ago

Create new Linux builds with the updater disabled

Categories

(Infrastructure & Operations Graveyard :: CIDuty, task)

x86_64
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1436457

People

(Reporter: mkaply, Unassigned)

References

(Blocks 1 open bug)

Details

We're investigating creating Snaps and Flatpaks for our Linux distros.

Since Snaps and Flatpaks handle their own updating, we'll need to start producing builds of Linux that have:

ac_add_options --disable-updater

Otherwise, these will be standard versions of Firefox. Both Snap and Flatpak simply repackage our existing builds, they do not require any code changes.

Once we have these packages, we'll investigate creating flatpaks and snaps as part of our standard builds.
Another note.

We'll need to be able to build partner distributions with these (to add distribution.ini).
Blocks: flatpak
We could simply disable the updater via a pref instead of disabling it in the build system.
(In reply to Chris AtLee [:catlee] from comment #2)
> We could simply disable the updater via a pref instead of disabling it in
> the build system.

The preference doesn't really do enough. It still leaves all the UI behind in preferences and text in the about dialog about the updater being disabled.

I think we are going to need some other build options for Flatpak anyway.

See bug 1332404
Still needed? Are we still pursuing flatpaks?
Flags: needinfo?(mozilla)
> Still needed? Are we still pursuing flatpaks?

Yes, we are still planning to do Flatpaks. Other things have moved to the front right now.
Flags: needinfo?(mozilla)
We're going to do this at runtime.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.