Difference between revisions of "Packaging ioquake3"

From ioquake3 wiki
Jump to: navigation, search
(reasons why mojosetup isn't used)
Line 9: Line 9:
 
** [http://ioquake3.org/files/installer_stuff/nemoders_ioq3_mojo.tar.bz2 Here] is the first attempt at mojo_setup (thanks to Nemoder!)
 
** [http://ioquake3.org/files/installer_stuff/nemoders_ioq3_mojo.tar.bz2 Here] is the first attempt at mojo_setup (thanks to Nemoder!)
 
*** However, Currently we use loki_setup
 
*** However, Currently we use loki_setup
**** BLEH.
+
**** Angst needs mojosetup packaged in the openSUSE buildservice to build installers
 +
**** mojosetup doesn't support components that can be used by mods
  
 
Things to help out packagers:
 
Things to help out packagers:

Revision as of 02:48, 29 October 2009

Packaging ioquake3 should be as easy as possible. I'd like to get a standard installer for all three platforms. But that probably isn't possible. So right now the ideal installers per-platform are:

  • NSIS for Windows.
    • Currently this is missing some ioquake3 logos.
  •  ??? for OS X
    • Currently all we can do is generate a .dmg at best. I'd like to have something better.
  • MojoSetup for Linux
    • Here is the first attempt at mojo_setup (thanks to Nemoder!)
      • However, Currently we use loki_setup
        • Angst needs mojosetup packaged in the openSUSE buildservice to build installers
        • mojosetup doesn't support components that can be used by mods

Things to help out packagers:

List of features that every installer needs

Where is pak0.pk3 on the disc?

ioquake3's logo in svg