Difference between revisions of "OSGeo Binary Distribution"

From OSGeo
Jump to navigation Jump to search
(Merged info into this page from: Distribution_Special_Interest_Groups and deprecated the other page.)
Line 54: Line 54:
 
Unlike the Debian-GIS SIG, which already has mailing list / code repository infrastructure, the RPM-using community does not have such infrastructure and would benefit from hosting by OSGeo.
 
Unlike the Debian-GIS SIG, which already has mailing list / code repository infrastructure, the RPM-using community does not have such infrastructure and would benefit from hosting by OSGeo.
  
= GIS Virtual Machine =
+
== GIS Virtual Machine ==
 
http://gisvm.com/
 
http://gisvm.com/
  
Line 88: Line 88:
 
* [http://postgis.refractions.net/rpms/ PostGIS RPMs for Fedora] from [http://www.refractions.net/ Refractions Research]
 
* [http://postgis.refractions.net/rpms/ PostGIS RPMs for Fedora] from [http://www.refractions.net/ Refractions Research]
 
* [http://www.gdf-hannover.de/software Mandriva and SuSe RPMs] -- maintained by GDF Hannover
 
* [http://www.gdf-hannover.de/software Mandriva and SuSe RPMs] -- maintained by GDF Hannover
 +
 +
== Enterprise Linux and derivatives (RHEL/CentOS/Scientific Linux) ==
 +
See [[Enterprise Linux GIS]]
  
 
= Old Technical Notes =
 
= Old Technical Notes =

Revision as of 01:22, 3 June 2010

This provides the status of current and historical binary packaging of OSGeo software, with the ultimate goal of OSGeo "branded and certified" binary distributions of open source geospatial software for Windows, Linux and possibly MacOS X and Solaris.

Objectives

  • Offer a painless user experience installing and getting started with OSGeo products.
  • Support major operating systems. In order of precedence that likely means Windows, Linux (Intel32), MacOS X and Solaris (Sparc).
  • Ensure that all components are inter-compatible avoiding version incompatibility hell.
  • Allow progressive installation, with packages pulled over the internet as requested. So the person can install a few packages without having to download everything, and so they can go back and add more packages later.
  • Provide an easy to use GUI installer.
  • Be relatively distribution/version agnostic - on linux we hope the same binaries will work on Debian, Fedora Core, Suse, Ubuntu, etc. On windows and MacOS X we hope the binaries would work across a variety of relatively recent OS versions.
  • Include at least all the OSGeo project software as packages, and dependencies of those packages.
  • Suitable for desktop and web service folks.
  • Provide a level of quality control
  • Simplify the process for projects to update and maintain the various distributions
  • Open channels of communication between packagers and application developers.

Windows distributions

OSGeo4W

OSGeo4W is a windows based stack of GeoFOSS which is based upon cygwin.

Goal: Ease of installation of the whole GeoFOSS stack in windows.

Status: Aug '08: Actively maintained by community, Works well

  • Pros:
    • Has already packaged many of the key GeoFOSS applications.
    • Likely to release first major release at FOSS4G 2008, 29 Sep 2008.
    • Has strong developer community.
  • Con
    • Needs installation
    • Needs internet connection for installation

PortableGIS

PortableGIS is a collection of GeoFOSS applications that run from a USB stick.

Goal: Have the most important applications always with you.

Status: Actively maintained by one person, (Jo Cook)

  • Pro
    • No installation required, just run the applications
  • Con
    • Doesn't work right from CD at the moment
    • Applications need clean-up (Eg. Java is bundled more than once)
    • Only one maintainer
    • Project development infrastructure not set up yet.
    • Would benefit by alignment with similar projects.
    • PortableGIS currently needs to be run from a writable medium (like and USB stick), it won't work on a read-only medium like a CD.

Linux

Unlike the Debian-GIS SIG, which already has mailing list / code repository infrastructure, the RPM-using community does not have such infrastructure and would benefit from hosting by OSGeo.

GIS Virtual Machine

http://gisvm.com/

  • Has a stable Virtual Machine, packaged in November 2008, based upon Ubuntu 8.10.
  • A new version is being developed for FOSS4G in October 2009.

Live CD\DVD

See the Live GIS Disc

Debian Linux

  • DebianGIS is about improving Debian to make it the best distribution for Geographical Information Systems applications and users. A good deal of GIS related softwares and libraries (e.g. GRASS) are already present in Debian. We have currently an up-to-date GRASS package in main and many other packages.

Ubuntu Linux

GeoLivre Linux

Gentoo Linux

Mandriva Linux

RPM-based distributions, such as Fedora Linux and SuSE Linux, do not have a dedicated GIS teams, but there are several parties maintaining independent RPM archives that could be persuaded to band their efforts together under the aegis of the foundation:

Fedora Linux

Enterprise Linux and derivatives (RHEL/CentOS/Scientific Linux)

See Enterprise Linux GIS

Old Technical Notes

  • I think building on the existing [FGS] infrastructure Linux (and possibly other Unix platforms) is attractive. See FGSDevNotes.
  • I think the existing MS4W package could potentially be a base for windows distribution.
  • William Kyngesburye has done a great deal of work producing MacOS X framework-style packages of GDAL, MapServer, GRASS etc for MacOS X ( http://www.kyngchaos.com/ ).
  • GDF Hannover has build RPMs for various Linux distros: http://www.gdf-hannover.de/software This could be a starting point
  • Osaka City University has built RPMs for Mandriva Linux distros: http://wgrass.media.osaka-cu.ac.jp/foss4g/downloads This could be a starting point too
  • Stephan Holl/GDF has written a GUI installer for QGIS0.8 with winGRASS-native integrated (MS-Windows).


References

  • Binary Package Listing - an attempt to make a single page pointing to all the currently available binary (and source) packages for each project
  • Binary Stack Platforms - a list of a few platforms where stacks are already (or could) be built upon