Oolite Bulletins

The latest release is working now.

I think adding this somewhere in the flatpak build process should make things work

It works when explicitly running the wrapper script with flatpak run --command=run_oolite.sh space.oolite.Oolite . I think this is because the .desktop file still uses the oolite binary: ❯ cat /var/lib/flatpak/app/space.oolite.Oolite/current/active/export/share/applications/space.oolite.Oolite.deskt...

Saves and OXPs aren't persisted for me. I ran flatpak enter space.oolite.Oolite bash while oolite was running, and everything was saved in $HOME as seen from inside the sandbox. ❯ flatpak enter space.oolite.Oolite bash bash-5.3$ ls GNUstep oolite-saves bash-5.3$ ls -R .: GNUstep oolite-saves ./GNUst...

I 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/ManagedAddOn...

I haven't actually tested the PR, but I read through the changes and it looks like it should work.

The 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 deve...

It 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.

MrFlibble, 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? I could reproduce the ...

Which version of Linux did you install? Fedora on bare metal. I have a t2 (2018-2020 intel) mac so it needed a patched kernel and stuff , but after installing it works the same as a normal linux install. I think using a normal distro works on older intel macs without any patches, you can just downl...

I had to use gnustep 1.28, but modern gcc and gnustep-make worked for me. I'm not sure how much stuff from linux-deps ends up being used. By "legacy" I meant that it doesn't follow modern linux desktop conventions and that I don't know any new codebases using it, so there isn't much intere...

I rebased the flatpak onto master, it crashes at startup or soon after with this error: oolite: Uncaught exception NSInternalInconsistencyException, reason: src/Core/OOWeakSet.m:168 Assertion failed in OOWeakSet(instance), method addObject:. Attempt to add object to OOWeakSet which does not conform ...

An aside. I found that my build of the Flatpak 1.91 'traps' the mouse in windowed mode. I wonder if that's due to using a system library rather than one of the 'ancient tweaked' ones. I just saw this thread, im going to to figure out what happened. I think I only tested in fullscreen mode. Im also ...

It failed miserably, when compiling clang segfaulted for some reason. I didn't even want to try to figure out what happened since its definitely something deep in the internals of how clang parses legacy code. Also I installed linux on my mac so I don't even have modern macos to test anymore.

https://packages.fedoraproject.org/pkgs/libdispatch/libdispatch/. Fedora builds it from source with up to date dependencies, so it should be possible. You can look at the .spec file for the exact instructions used. Also I compiled gnustep for the flatpak from a source tarball and it just worked usin...