Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi Olivier,

On 2012-01-05 at 16:38 -0200, Olivier Hallot wrote:

So, what you want to do is to put the new version to your server (let's
say http://yourserver/newersion.msi) together with the following xml
(located at http://yourserver/update.xml):

<?xml version="1.0" encoding="utf-8"?>
<inst:description xmlns:inst="http://update.libreoffice.org/description";>
  <inst:id>LibreOffice 3.something</inst:id>
  <inst:version>3.something</inst:version>
  <inst:gitid>123456-abcdef-1a2b3c-4d5e6f</inst:gitid>
  <inst:os>Windows</inst:os>
  <inst:arch>x86</inst:arch>

  <inst:update type="application/octet-stream" src="http://yourserver/newersion.msi"; />
</inst:description>

where inst:gitid is the value of 'buildid' in program/versionrc of
newersion.msi when installed.

The last step is to point your installations to this update xml, and
that is by modifying UpdateURL to value http://yourserver/update.xml in
program/versionrc of your installations.

Does this work for you?

I think the scheme you listed will be OK. But I don't have a server to
test in an internal network

Ah - OK; for testing you should be able to do that locally too, using
file:// protocol (ie. locate the files eg. in /tmp/newversion.msi,
and /tmp/update.xml, and use file:///tmp/newversion.msi resp.
file:///tmp/update.xml in the examples above).

Hope it works for you :-)

Regards,
Kendy


Context


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.