Thanks, I'll build 0.2.12b and copy it over 0.2.12a then.
The data wasn't updated for the 0.2.12a/b tags.
http://glestae.svn.sourceforge.net/viewvc/glestae/branches/0.2.x/data/game/
That looks to be up to date.
Installing 0.2.12b over 0.2.12a should work.
PS: I've updated my last post to be clearer about what is included.
How about using
Autopackage for the Linux installer. The project's site is under reconstruction so there's not much info about it at this moment.
But in brief, here is how it proceeds when you run an autopackage-installer:
1. Checks to see if the Autopackage Software Manager (graphical software manager, pretty much like synaptic for .deb's or urpmi or yum for .rpm's) is already installed in the system;
1a.1. If the ASM is not yet installed on your system, the user is prompted (in a text terminal) if he/she wants to download and install it - clicking yes will perform these actions.
1a.2. The script simply hands control of the installation to it and that's it.
1b. If the AMW is already on your system, the script simply hands control of the installation to it and that's it.
This is why an autopackage adds barely no oversize to the actual package: the included installer is a minimal script to just install the actual installer which is a powerful tool that can be used for any other autopackage package in the future!
You download the actual installer ONCE! All you download from then on are the actual applications you want on your system! 2. The actual installer (ASM)
checks for dependencies (they may have been installed through your distro's standard software manager)
and automatically advises to, downloads and installs the missing dependencies! (I am unsure whether it installs them using your standard software manager or rather downloads and builds them all regardless of)
3. The application you want to install (e.g. GAE) is built from source and installed for you! This is the best way to have a program working at its best for your machine, as it was built with the libraries you have on the machine it'll be used on. Of course, it is also the less user-friendly way to install something on your system. Or rather
was til you use autopackage.
4. The installer takes care of integration to your desktop, namely placing menu-items, for the Autopackage Package Manager (in your system menu as 3rd Party Applications) as well as for the application you installed with it.
5. The Package Manager let's you uninstall the autopackage programs you installed just as easily as you would uninstall from a .deb or .rpm.
For the end-user, it's a great way to have a package effortlessly installed to suit your system.
For the developper (I suppose it won't be harder than configuring another installer?) it's easy to publish new releases in one package only, regardless of architecture (32 or 64 bit, though I guess a PowerPC and other architectures might also work, just as long as they're running Linux) and Linux ditro.
Just a thought, you might want to take a look at it for the next GAE release.
EDIT: Added link to the Autopackage site on my first reference to it.