Detect and run modern installations

[Lone_Wolf]

Just checked with latest trunk (source build) and the version is indeed only shown on the start screen and in the log files .

I would expect the -showversion option to output the version on stdout and then stop .
(similar to what the the --help option does) .

[another_commander]

-showversion was never designed to output the game version externally.

Can one not use the --help output to grab the version string? We have it in trunk and 1.92.1 right now.

[MrFlibble]

--help seems to work fine with appimage

Code: Select all

$ ./Oolite_test_1.92.1.7800-260303-6443c4c-x86_64.AppImage --help 2>/dev/null | sed -n 's/^Version //p'
1.92.1.7800-260303-6443c4c

[hiran]

--help seems to work fine with appimage

Code: Select all

$ ./Oolite_test_1.92.1.7800-260303-6443c4c-x86_64.AppImage --help 2>/dev/null | sed -n 's/^Version //p'
1.92.1.7800-260303-6443c4c

Yep, that works. So it is at least not necessary to extract the image for version information.

Now I need a better way to test for the debug capability. Currently that still requires to extract the manifest.plist file. Could that information be added to the help screen as well?

Just to recap: We used to offer releases and developer releases. Here is the description of the developer release as I retrieved it from
https://web.archive.org/web/20230329124 ... /download/

Code: Select all

OXP Developer releases

The main downloads are optimised for maximum in-game performance and are recommended for players. People wishing to develop expansion packs for the game are recommended to install the OXP Developer releases. The following extra features are enabled in these releases at the expense of performance.

    Debug OXP and Debug Console are supported.

    On all platforms, installing Debug.oxp enables support for external console applications using the Oolite debug console TCP protocol. OoDebugConsole1.6.zip is an example of a cross-platform, python based, external console application. It contains a precompiled console for windows based computers, and the original python based console for Linux and Posix compliant computers.
    OXP Verifier functionality is included.
    OXP Deprecation warnings are enabled.
    Localization tools support is included.
    AI Graphviz support is included.
    Debug information is added. (e.g. AI stack, collision, dump target state, entities, memory usage, script tracing etc.)
    JS monitor support is enabled.
    The JS method takeSnapshot() is enabled.
    Time Acceleration Factor (TAF) is enabled.
    Shift-F displays FPS, entities, coordinates and TAF info.
    Sanity checks are included.

[MrFlibble]

--help seems to work fine with appimage

Code: Select all

$ ./Oolite_test_1.92.1.7800-260303-6443c4c-x86_64.AppImage --help 2>/dev/null | sed -n 's/^Version //p'
1.92.1.7800-260303-6443c4c

Yep, that works. So it is at least not necessary to extract the image for version information.

Now I need a better way to test for the debug capability. Currently that still requires to extract the manifest.plist file.

Short of augmenting the --help, I can only find this crude method, which probably won't work on ancient versions.

Code: Select all

timeout 5 ./Oolitewhatever.AppImage -verify-oxp /tmp/notreal -nosplash && echo debug || echo nodebug

This unfortunately spawns a window in non-test versions, and I expect a shorter timeout is likely to give false results on slow systems.

If the --help was improved to add debug/test/vanilla, either as an extra line, or as part of the version string, the absence of either would indicate an old enough version that one would have to declare in Starter whether or not that version had debug, as you have done so far, else it could be automagic, as I expect is your intent.

[hiran]

Now I need a better way to test for the debug capability. Currently that still requires to extract the manifest.plist file.

Short of augmenting the --help, I can only find this crude method, which probably won't work on ancient versions.

Code: Select all

timeout 5 ./Oolitewhatever.AppImage -verify-oxp /tmp/notreal -nosplash && echo debug || echo nodebug

This unfortunately spawns a window in non-test versions, and I expect a shorter timeout is likely to give false results on slow systems.

If the --help was improved to add debug/test/vanilla, either as an extra line, or as part of the version string, the absence of either would indicate an old enough version that one would have to declare in Starter whether or not that version had debug, as you have done so far, else it could be automagic, as I expect is your intent.

You're spot on guessing my intent. And I like the idea of adding a line to the help screen. It is meaningful to users and OoliteStarter alike.

[another_commander]

Line added to help screen. You can now see if you are running a debug-functionality-enabled (test release) build or not.

[hiran]

Line added to help screen. You can now see if you are running a debug-functionality-enabled (test release) build or not.

Thank you for that change. This works, and it is backward compatible. Versions that do not disclose their build type still won't go interactive.
I enhanced OoliteStarter to make use of that feature.