Binary Stack Platforms

The development of a primary OSGeo Binary Distribution was proposed earlier. There are several possible approaches to meeting this need. This section discusses a few different approaches.

Full Multiplatform Binary stack
This is a dream for a good binary stack. A platform to compile all source codes that can be used for all OS.

Starkits
A good example is Starkit. A Starkit is a wrapping mechanism named after "STandAlone Runtime Kit" for delivering an application in a self-contained, installation-free, and portable way.
 * Using Starkits for application deployment - good intro article

pro

 * self-contained, installation-free, and portable way

cons

 * all libraries in one installer. Static compilation.
 * the most expensive (time, money, know how) to maintain.

MS4W
The no fuss installer for setting up MapServer on Microsoft Windows platforms. The purpose of this package is to allow all levels of MapServer users to quickly install a working environment for MapServer development on Windows. It is also an environment for packaging and distributing MapServer applications

cons

 * only windows oriented

OSGeo4W
The OSGeo installer for setting up most OSGeo related software on Microsoft Windows platforms. The purpose of this package is to allow all levels of users to quickly install a working environment for use and development on Windows.

pro

 * Ensure versions of software that can work together, eg. QGIS+GDAL+GRASS+Python

cons

 * only windows oriented

FGS
The FGS Linux Installer is a self-extracting file that will install MapServer with PHP/MapScript and all of their dependencies on your Linux system. It provides a stand-alone environment with all the required software (incl. Apache and PHP) to run PHP/MapScript webmapping applications. The bundled version of Apache can be configured to run on any port so it will not interfere with previous installations of Apache or other web servers on your system.

cons

 * only linux oriented

Linux packages repositories
Package repositories are normaly maintained by specialist who prepare packages for personal use and for the community. GIS packages are normally not available in official distributions that's why there's the need for an external repository.


 * Debian GIS Project page
 * Ubuntu GIS page
 * OpenSuse
 * Enterprise Linux (ELGEO) - Red Hat/Centos/Fedora

pro

 * package maintainance is centralized
 * fast install in specific Linux distributions
 * posibility to create a cental OSGeo repository

cons

 * too many linux distributions to maintain all packages for all of them

LiveCD
Based on Linux, LiveCDs are a complete operating system contained is a single CD. There's no need to install it on the local machine, only a boot from CD drive is needed to experience the configured LiveCD.


 * | OSGeo Live
 * Google search page for GIS LiveCD.

pro

 * optimized configuration of all application inside a single environment.
 * no risk of library collisions as when installing multiple sofwares on the same machine.
 * less expensive to maintain: a good linux hacker with some experience of liveCD can maintain different versions without a big effort.
 * useful for presentations, workshops, demos, and university classroom. No need to configure many computers.

cons

 * based only on one OS (Linux).
 * Need to download an entire ISO (700 MB ca.)