Development/Test Update Check

Configure the build with, of course.

There is a testing update server at the fake URL. To make that work on your machine, it needs to resolve  to the same IP address as , namely. On Unix-like systems that can be done by adding a line

195.135.221.70 update-test.libreoffice.org

to, for example.

That testing update server runs a copy of patched with diff --git a/check.php b/check.php index 64c23f1..0c612a5 100644 --- a/check.php +++ b/check.php @@ -273,8 +273,7 @@ $update_map = array( function print_update_xml($buildid, $os, $arch, $lang, $pkgfmt) {    global $build_hash_to_version, $update_map, $localize_map, $debug; -    if(!array_key_exists($buildid, $build_hash_to_version) -      || $buildid == $update_map['stable']['gitid'] +   if($buildid == $update_map['stable']['gitid']        || $buildid == $update_map['latest']['gitid']     ) { error('No update for your LibreOffice version.'); @@ -295,7 +294,8 @@ function print_update_xml($buildid, $os, $arch, $lang, $pkgfmt) { -   $user_ver = explode( '.', $build_hash_to_version[$buildid] ); +   $userver = '0.0.0.0'; +   $user_ver = explode( '.', $userver ); $latest_ver = explode( '.', $update_map['latest']['version'] ); if ($latest_ver[2] >= $user_ver[2]) { # third digit at index 2 @@ -305,7 +305,7 @@ function print_update_xml($buildid, $os, $arch, $lang, $pkgfmt) { }    # don't downgrade RC/prerelease users -   if(version_compare($new['version'], substr($build_hash_to_version[$buildid], 0, 5), '<')) { +   if(version_compare($new['version'], substr($userver, 0, 5), '<')) { error('No update for your LibreOffice version.'); } which fakes the incoming LibreOffice version to be  (unless it happens to have an &ldquo;official&rdquo;   that is listed in   in  ), so the update server considers it older than its latest version (which happens to be 4.1.2).
 * 1)    print "ver : " . $build_hash_to_version[$buildid] . " - ".
 * 2)    	   $update_map['latest']['version'] . "\n";

To run a LibreOffice installation against that testing update server, change the  line in its   ini-file (e.g.,   on Linux) from using   to using. Since, on platforms other than Windows, for an (implicitly)  build the &ldquo; &rdquo; at the end of that line will be empty; complete it manually with the correct package format (e.g., &ldquo; &rdquo; or &ldquo; &rdquo; for Linux, &ldquo; &rdquo; for macOS X).

Then, let the automatic, timer-triggered check kick in or run it manually via.