111–120 of 176 posts
Earlier quoted context omitted.
This comment doesn’t make any sense. Installing a deb file is done with apt, what are you actually referring to when you say “apt-get install”?
apt, apt-get, aptitude and synaptic are all front ends to the same package management system.
Earlier quoted context omitted.
I'm pretty sure that forced restart is from the snap package, and you don't have that without snap.
Nope. There are many weird things about snap, but it actually handles Firefox updates very smoothly.
Takes 7 steps to install Firefox this way as opposed to apt-get install.
1. Add the apt repo 2. Add the repo's public key 3. apt-get update 4. apt-get install firefox What 3 steps am I missing?
Earlier quoted context omitted.
In case of security fixes, you will stay unpatched for a bit less time. ESR is intended for places that really don't like any form of change like rigid enterprises and banks and such. End users should probably steer clear of that unless they have a good reason not to; which they generally don't. Except for a false sense of security. I personally don't see a good reason to opt out of security changes for any longer th…
I don't see a problem waiting for alpha- and beta-testing to finish first before the new code is distributed to actual normal users . Note, the "normal users" you describe are involuntary testers who got forced into the role because keeping testers on the payroll is so last century.
Earlier quoted context omitted.
The tar.gz build has exactly the same problem (it just doesn't complain about it): it needs to close the files from the old package and open the ones from the new package. Hence the restart. You can minimize the downtime by just restarting the browser and then using History | Restore previous session. The flatpak build avoids this problem by keeping both versions on the disk, up until you stop the app. Only at this t…
> it just doesn't complain about it This is the key point. I'm assuming that it downloads the update and then waits for me to agree to install it, but however it works it doesn't interrupt my browsing while I'm in the middle of something.
It's not an issue for these .deb packages because they enable the (experimental) forkserver.
Earlier quoted context omitted.
The tar.gz build has exactly the same problem (it just doesn't complain about it): it needs to close the files from the old package and open the ones from the new package. Hence the restart. You can minimize the downtime by just restarting the browser and then using History | Restore previous session. The flatpak build avoids this problem by keeping both versions on the disk, up until you stop the app. Only at this t…
The deb version does more than complain, it can also crash and have tabs crash due to needing restart.
Ubuntu likes to replace installed debs with snaps without consulting the user and you need to configure it not to do so.
And the profile folder for the snap is in a different place than for the deb, so make a copy of it etc.
I'm not going into full detail as these things are easily found via Google as long as you're aware of them.
They don't seem to be packaging the LTS version, Firefox ESR. Am I missing something? Is there a separate Mozilla repository for that?
They're already done by the Debian people.