[niffiwan]

I've finally got around to finishing this off - FSO RPMs for Fedora 17.  The spec file is hopefully generic enough that it should be usable (perhaps with minor tweaks) on any distro that uses RPMs (e.g. OpenSuse)

Fedora 17 i686
Fedora 17 x86_64
Fedora 17 i686 debuginfo
Fedora 17 x86_64 debuginfo
Fedora 17 source RPM


Here's the GPG public key used to sign the RPMs .  To import the key:

Code: (run in a terminal) [Select]

sudo rpm --import niffiwan.pubkey

To verify the RPMs:

Code: (run in a terminal) [Select]

rpm -K *.rpm

To install:

Code: (run in a terminal) [Select]

sudo yum localinstall *.rpm

Now, some notes

1) This is just the FSO executables (release & debug), there's no data included whatsoever (no media_vps, no mods, etc)
2) The debuginfo RPMs contain debugging symbols, unless you're a coder or are trying to catch a stacktrace, don't worry about them.
3) wxlauncher doesn't yet support executables in a different directory to the game data, my suggestion for now is to softlink these executables to your game data directory by doing something like:

Code: (run in a terminal) [Select]

cd ~/freespace2
ln -s /usr/bin/fs2_open_3.6.14
ln -s /usr/bin/fs2_open_3.6.14_DEBUG

Any feedback on these packages is much appreciated.

ps. and yes, creating Ubuntu .debs would probably have been useful for more people, but I'm waaaaay more familiar with RPMs, so they got done 1st - .debs are next on the list when I get time   (and when I feel like creating 8 more VMs in order to build/test everything!! )

[chief1983]

And when .16 is out we just need a Diaspora game data RPM that depends on it and you're set

[niffiwan]

Yeah - TCs are easier to package than Freespace2, getting the retail data installed in an automated fashion is tricky

[chief1983]

Plus it costs money to acquire

[LordMelvin]

Is there any way to set up a script to run cabextract or something similar on the GoG installer exe? That'd work for >90% of new cases, I'd expect.

[niffiwan]

you can setup scripts (pre/post install) in the RPMs, where would the dependencies go I wonder... perhaps have a "dummy" fs2retail package that just runs scripts to extract the VPs (etc) and maybe checksums them...