On 2010-10-06 7:00 PM, Jon Hamkins wrote:
The way this works is LibO would publish delta RPMs that contain all
the differences from the previous release, and then the users yum
package manager would download the delta RPM, build the full RPM from
it, and install.
Excellent points, and there's the rub. OOo has never (at least to my
knowledge) provided delta updates of any kind.
So the key will be providing this mechanism on the back-end, then just
publish instructions for the different platforms/package managers.
And since Windows is the only one of those platforms that doesn't have a
proper package manager, the current internal 'updater' could become a
Windows-only true 'Updater'.
--
Best regards,
Charles
--
To unsubscribe, send an empty e-mail to discuss+unsubscribe@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/
Context
- Re: [tdf-discuss] Automatic Updates (continued)
- Re: [tdf-discuss] Automatic Updates · Charles Marcus
Re: [tdf-discuss] Automatic Updates · Erich Christian
Re: [tdf-discuss] Automatic Updates · Jean Hollis Weber
Re: [tdf-discuss] Automatic Updates · Scott Furry
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.