For information and discussion about Oolite.
https://bb.oolite.space/
You might use strace to see what's pulled in. It'll need to be inserted in the script that launches the binary.sharpenedblade wrote: ↑Thu Jul 24, 2025 12:44 amMrFlibble, I build your fork as a flatpak (see the flatpak-new-linux-deps branch in my fork) and it looks like it works the same as master when I tested. I don't know if Oolite is using its bundled libs or the "system" (flatpak runtime) libs, is there a way to check?
Using your work as a starting point (thanks for all you did!), I have managed to get the Oolite flatpak working locally with the modern build. (It is not on flathub.)sharpenedblade wrote: ↑Thu Jul 24, 2025 11:31 pmIt was using the bundled libs. Also it still works if I delete every .so file except for libjs_static.a, so thats what im using in the flatpak now because the runtime can keep things up to date automatically.
flatpak run org.OoliteProject.oolite. Flatpak put the game folders, GNUstep, oolite-saves and .Oolite in ~/.var/app/org.OoliteProject.oolite/. I could save and load a game. I could also add OXPs in the game and an OXP I put in ~/.var/app/org.OoliteProject.oolite/.Oolite/AddOns was correctly loaded. Code: Select all
https://github.com/mcarans/oolite/blob/flatpak/installers/flatpak/org.OoliteProject.oolite.yamlThanks, that's helpful to know. I had taken ooliteproject from the GitHub organisation name. I had wondered why you chose space.oolite.Oolite, but that's clear now and I will change to that.sharpenedblade wrote: ↑Tue Dec 23, 2025 11:18 pmThe new package is org.ooliteproject.Oolite, but I don't think the domain ooliteproject.org is registered (If I'm wrong and it is actually used by oolite then you can ignore this). Its better to use space.oolite.Oolite because flatpaks are expected to be under a domain that is controlled by the developer, if someone else buys the ooliteproject.org domain and releases a flatpak on flathub under that domain it will cause problems because you can not have multiple flatpaks with the same identifier installed, even if they are from different remotes.
Flatpak redone including Oolite directly using correct folders (~/.var/space.oolite.Oolite/...) in this PR:sharpenedblade wrote: ↑Tue Dec 23, 2025 11:18 pmThe new package is org.ooliteproject.Oolite, but I don't think the domain ooliteproject.org is registered (If I'm wrong and it is actually used by oolite then you can ignore this). Its better to use space.oolite.Oolite because flatpaks are expected to be under a domain that is controlled by the developer, if someone else buys the ooliteproject.org domain and releases a flatpak on flathub under that domain it will cause problems because you can not have multiple flatpaks with the same identifier installed, even if they are from different remotes.
Please can you see if there are any folders insharpenedblade wrote: ↑Thu Jan 08, 2026 9:07 pmI tested 1.91.0.7734-260108-81282f8, the actual game is working fine (I tested a new save and the OXP manager), but data isn't persisted across restarts now. Saves are at ~/oolite-saves and the GNUStep folder is at ~/GNUStep (including OXPs at ~/GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns/), so they are lost when the flatpak exits. By default flatpak only saves XDG_CONFIG_HOME, XDG_DATA_HOME, XDG_CACHE_HOME, and XDG_STATE_HOME which are all paths under ~/.var/app/space.oolite.Oolite.
~/.var/app/space.oolite.Oolite/. That is where it saves for me. The startup script should detect flatpak and use that folder. ~/oolite-saves, ~/GNUStep etc. are not mapped using persist.~/.var/app/space.oolite.Oolite/.ManagedAddOns/flatpak enter space.oolite.Oolite bash while oolite was running, and everything was saved in $HOME as seen from inside the sandbox.Code: Select all
❯ flatpak enter space.oolite.Oolite bash
bash-5.3$ ls
GNUstep oolite-saves
bash-5.3$ ls -R
.:
GNUstep oolite-saves
./GNUstep:
Defaults Library
./GNUstep/Defaults:
OoliteDefaults.plist
./GNUstep/Library:
ApplicationSupport Caches
./GNUstep/Library/ApplicationSupport:
Oolite
./GNUstep/Library/ApplicationSupport/Oolite:
ManagedAddOns
./GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns:
oolite.oxp.Switeck.Cargo-Contract-Mod.oxz
./GNUstep/Library/Caches:
org.aegidian.oolite
./GNUstep/Library/Caches/org.aegidian.oolite:
Oolite-cache.plist Oolite-manifests.plist
./oolite-saves:
Jameson.oolite-save
Code: Select all
❯ fd -u . --exclude cache ~/.var/app/space.oolite.Oolite/
/home/abcd/.var/app/space.oolite.Oolite/.ld.so/
/home/abcd/.var/app/space.oolite.Oolite/.ld.so/a6d674d53e3e2e4578fe249edf4441c9d69df7ea5e65a30b2d3d6229c8e23576
/home/abcd/.var/app/space.oolite.Oolite/.ld.so/active
/home/abcd/.var/app/space.oolite.Oolite/.local/
/home/abcd/.var/app/space.oolite.Oolite/.local/state/
/home/abcd/.var/app/space.oolite.Oolite/config/
/home/abcd/.var/app/space.oolite.Oolite/config/pulse/
/home/abcd/.var/app/space.oolite.Oolite/config/pulse/cookie
/home/abcd/.var/app/space.oolite.Oolite/data/
Please try the following:sharpenedblade wrote: ↑Fri Jan 09, 2026 4:20 amSaves and OXPs aren't persisted for me. I ranflatpak enter space.oolite.Oolite bashwhile oolite was running, and everything was saved in $HOME as seen from inside the sandbox.
Below is what is actually saved on the host system (I ignored cache because the only thing in there is a bunch of mesa files)Code: Select all
❯ flatpak enter space.oolite.Oolite bash bash-5.3$ ls GNUstep oolite-saves bash-5.3$ ls -R .: GNUstep oolite-saves ./GNUstep: Defaults Library ./GNUstep/Defaults: OoliteDefaults.plist ./GNUstep/Library: ApplicationSupport Caches ./GNUstep/Library/ApplicationSupport: Oolite ./GNUstep/Library/ApplicationSupport/Oolite: ManagedAddOns ./GNUstep/Library/ApplicationSupport/Oolite/ManagedAddOns: oolite.oxp.Switeck.Cargo-Contract-Mod.oxz ./GNUstep/Library/Caches: org.aegidian.oolite ./GNUstep/Library/Caches/org.aegidian.oolite: Oolite-cache.plist Oolite-manifests.plist ./oolite-saves: Jameson.oolite-save
Code: Select all
❯ fd -u . --exclude cache ~/.var/app/space.oolite.Oolite/ /home/abcd/.var/app/space.oolite.Oolite/.ld.so/ /home/abcd/.var/app/space.oolite.Oolite/.ld.so/a6d674d53e3e2e4578fe249edf4441c9d69df7ea5e65a30b2d3d6229c8e23576 /home/abcd/.var/app/space.oolite.Oolite/.ld.so/active /home/abcd/.var/app/space.oolite.Oolite/.local/ /home/abcd/.var/app/space.oolite.Oolite/.local/state/ /home/abcd/.var/app/space.oolite.Oolite/config/ /home/abcd/.var/app/space.oolite.Oolite/config/pulse/ /home/abcd/.var/app/space.oolite.Oolite/config/pulse/cookie /home/abcd/.var/app/space.oolite.Oolite/data/
flatpak run --command=run_oolite.sh space.oolite.Oolite. I think this is because the .desktop file still uses the oolite binary:Code: Select all
❯ cat /var/lib/flatpak/app/space.oolite.Oolite/current/active/export/share/applications/space.oolite.Oolite.desktop
[Desktop Entry]
Name=Oolite
Comment=An OpenGL Elite-like space game
Exec=/usr/bin/flatpak run --branch=master --arch=x86_64 --command=oolite space.oolite.Oolite
Icon=space.oolite.Oolite
Terminal=false
Type=Application
Categories=Game;Simulation;
StartupWMClass=oolite
X-Desktop-File-Install-Version=0.28
X-Flatpak=space.oolite.Oolite
Code: Select all
❯ flatpak run --command=sh space.oolite.Oolite
[📦 space.oolite.Oolite ~]$ echo $FLATPAK_ID
space.oolite.Oolite
[📦 space.oolite.Oolite ~]$ ls /app/bin
autogsdoc defaults gdomap HTMLLinker openapp pldes plser sfparse
classes espeak gnustep-config make_strings opentool plget plutil speak
cvtenc espeak-ng gnustep-tests notify-send pl plmerge Resources speak-ng
debugapp gdnc gspath oolite pl2link plparse run_oolite.sh xmlparse
[📦 space.oolite.Oolite ~]$ /app/bin/run_oolite.sh
2026-01-08 22:01:03.947 oolite[49:50] Truncating thread name 'OOLogOutputHandler logging thread' to 15 characters due to platform limitations