Bug Hunting Session
Bug 86985 - No auto-update on Windows. Please add a new auto-update and auto-install feature.
Summary: No auto-update on Windows. Please add a new auto-update and auto-install feat...
Status: RESOLVED DUPLICATE of bug 68274
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.3.2.2 release
Hardware: All Windows (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-03 19:08 UTC by Jeb Eldridge
Modified: 2014-12-04 16:41 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeb Eldridge 2014-12-03 19:08:49 UTC
There is currently no way for me to auto-update Libreoffice, thus I am stuck to being forced to perform an update the old fashioned way by either clicking "Check for Updates" in the app and going to the Libreoffice website that way or just by manually typing in the address in my web browser.
Not having an auto-update feature poses not only a halted progress risk, but also a security risk for users not apt to update their apps manually, which is frankly a LOT of Windows users because Windows doesn't auto-update apps unless it is written in the app code or the app is available and was originally downloaded in the Windows Store.

A quick fix to this issue would be to add all the LibreOffice apps and binaries to the Windows Store for Windows 8.x and up while having a separate version downloadable for Windows 7 and under directly on the Libreoffice website that contains all necessary binaries and permissions to auto-update.
Comment 1 Julien Nabet 2014-12-03 20:53:14 UTC
There's an auto-update but for the same branch.
I mean last stable current one is right now 4.3.4, 4.3.5 (both 4.3 branch) will be proposed but when 4.4.0 (4.4 branch) will be released, it won't be proposed.
Comment 2 Adolfo Jayme 2014-12-04 16:41:28 UTC
We could solve this by using Sparkle/WinSparkle instead of our inherited, half-baked implementation.

*** This bug has been marked as a duplicate of bug 68274 ***