While it is a good thing to see LO package size being shrinked, being able to perform partial updates would save a lot of time and of bandwidth for users. As a first idea, I would suggest something similar to what Firefox is doing (https://wiki.mozilla.org/UpdateGeneration): - When a minor release (mostly for security or stability reasons) is available (A.B.C to A.B.C+1), we should download only a partial update. - When a major release is available (new features), we should download a complete update or upgrade.
Very old request :-) I am pretty sure I have already seen the same request before but I can't find the bug report. Perhaps it was in the OOo time. Best regards. JBF
I was sure I had seen it before also, but couldn't find it either.
Additional details. (I've also updated the summary to make this easier to search for.) As a 100MB+ download, LibreOffice is inconvenient to update for even users with fast broadband and may be impossible to update for users with slow or unreliable connections, at least on a regular basis. The ideal resolution here is for the internal update mechanism to be able to download partial updates, much as Firefox does. For minor hotfixes this has the promise of massively reducing the required download size compared to downloading the complete installer. There's been some investigation of what is required for a Windows-only solution at AOO(i): http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201210.mbox/%3C50742228.5080002@googlemail.com%3E http://wiki.openoffice.org/wiki/Building_installation_packages This relies on Microsoft Installer, and so is not a general solution (which would need to be cross-platform, as Firefox's is), but may be a suitable stopgap for Windows users.
*** Bug 81914 has been marked as a duplicate of this bug. ***
*** Bug 88258 has been marked as a duplicate of this bug. ***
This ask.libreoffice question is also related. http://ask.libreoffice.org/en/question/18542/is-lo-planning-incremental-update/
*** Bug 89240 has been marked as a duplicate of this bug. ***
*** Bug 90619 has been marked as a duplicate of this bug. ***
The Sparkle/WinSparkle framework supports this feature. https://github.com/sparkle-project/Sparkle/wiki/Delta-Updates
Fedora's delta-rpm is worthing a look. https://www.suse.com/documentation/sles11/book_sle_admin/data/sec_rpm.html
*** Bug 96945 has been marked as a duplicate of this bug. ***
Please note "Incremental Windows Installer .MSP patches" at https://www.collaboraoffice.com/solutions/collabora-office/
a little house keeping: Bug 68274 - provide better update mechanism -- Mozilla ARchive (mar) based incrementals
Markus has been working on this for over a year and it is currently being tested on linux and windows. Blog Posts https://mmohrhard.wordpress.com/2017/08/22/announcing-automatically-updating-daily-windows-libreoffice-builds/ https://mmohrhard.wordpress.com/2017/06/21/announcing-automatically-updating-libreoffice-builds/ Updater Issues and Improvements https://wiki.documentfoundation.org/Development/Updater/SeeAlso Builds http://dev-builds.libreoffice.org/daily/master/Linux-archive-x86_64@80-updater/ http://dev-builds.libreoffice.org/daily/master/Win-x86@38-updater/
This is very outdated! I don't get it why a feature like this is not given more priority!!! I would prefer it to any other feature on libreoffice just because Of The security improvements it would bring. As a company, being assured that a specific software is updated is a way to have some peace of mind (not to mention always getting access to new features). On Linux we can have some of that peace, but not on our windows workstations. It's a really awfuljob to get to every computer and update libreoffice manually... Please consider moving this forward...
@ Maverick : LO is a volunteer driven project. Can you do it yourself? Feel free. You cannot? Then the message is "no-value". Please do not argue and respond, nothing will change, except that we can spend that time on a number of other issues. As already noted, there's a commercial solution for this. So this is not at all a priority.
Is this bug about: * Supporting automatic updates as opposed to manual ones, or * Supporting incremental/diff updates, regardless of whether those are performed manually or automatically? The title says one thing, the bug alias says another.
(In reply to Eyal Rozenberg from comment #17) > Is this bug about: Probably both, as, albeit they can be done separately, they make the most sense together, and it wouldn't be worth investing time and effort in just one aspect.