Are you saying the nightly puts itself somewhere else?
Okay, you guys convinced me to give it a try. And indeed it does put itself "somewhere else" ... into ~/.local/lib/Oolite-trunk instead of just .../Oolite. And the binary has "-trunk" appended too, which is very nice. Great job, guys!
Only my delight was short-lived:
./oolite.app/oolite: error while loading shared libraries: libGLU.so.1: cannot open shared object file: No such file or directory
Erk. It looks like Oolite-trunk died with an error. When making an error
report, please copy + paste the log above into the report.
Probably because my /usr/lib/libGLU.so.1 is "ELF 64-bit LSB shared object, x86-64", which I bet the 32-bit executable doesn't care for. In fact, I get a whole bunch of libs "not found" when I do an ldd on the binary. Oh well!
And you get a second menu shortcut, called oolite-trunk, next to the original shortcut.
Yes indeed you do, very nice!
In poking around before taking the leap, I found something that I probably read months ago and just forgot, which explains why (1) there's no 64-bit nightly build, and (2) why the developers figured I was too much of a chowderhead to reply to when I asked about it:
Currently, a native 64-bit build isn't available as a binary download because none of the developers has an amd64 system. If you are capable of building Oolite-Linux from source and have a suitable machine, it would be greatly appreciated if you can volunteer to be the maintainer of the amd64 build.
I might be willing to discuss providing a 64-bit build. I've certainly built oolite from source before, back in the 1.72 days, though I used its built-in Debian stuff rather than autopackage. Even though Debian is still currently shipping the obviously-broken libgnustep 1.19, I don't have any packages that depend on it, so could use any version you guys wanted me to try. (And yes, I realize that the source comes with its own copy of 1.16, which is fine too.)
I'm not entirely sure I'm quite ready to become "the maintainer of the 64-bit build", though. Sounds so formal and responsibility-like.
Maybe I should just grab the source, build it, and come back to talking once I have a working binary.