Enterprise Linux GIS
This page gathers links and information about running FLOSS GIS software on Enterprise Linux (shortened EL hereafter) and derivatives, that is Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux.
EL is a popular and robust platform for servers and computing-heavy workstations, and is therefore a good fit for the specific requirements of GIS.
Useful repositories for GIS software
- EPEL is a official Fedora project which repackages many Fedora packages which are not part of the standard EL distribution. It contains quite a few GIS packages and base libraries. Note that one of the rules of the packages maintained in EPEL is that they should never require to change the base EL distribution.
- PostgreSQL RPM Building Project maintains many versions of the PostgreSQL database as well as PostGIS packages
- ELGIS repository maintains versions of packages which cannot be maintained in EPEL. This is where our packaging effort currently takes place. It requires EPEL to be configured as a repository.
Packages Status Summary
|Package||Version (stable)||Version (testing)||Repository||Comment|
|gdal||1.6.3||1.7.2||elgis||testing is built against postgresql84|
|grass||6.4.0RC6||elgis||-wx UI broken since EPEL update to wxGTK/wxPython 2.8.11|
|postgis||1.5.1||elgis||built against postgresql84|
|qgis||1.4.0||elgis-plus||Python plugins not working, probably requires a higher version of Python|
How to enable the ELGIS repository
- enable the EPEL repository (see https://fedoraproject.org/wiki/EPEL/FAQ#howtouse)
- if you want to install QGIS, edit the /etc/yum.repos.d/elgis.repo file and enable the 'elgis-plus'. WARNING: this updates the base distribution
How to hack and locally build the custom packages
For the time being the custom packages (that is, those not maintained by EPEL) are versioned by and distributed through argeo.org.
You can see the currently versioned packages here (along with non-GIS packages maintained by argeo.org):
Note: the base URL will probably change in the near future
Note: simply accept the self-signed certificate
You can checkout all the packages:
Or one by one, for example:
Each package directory follows the directory structure expected by rpmbuild (see how to set an rpmbuild environment).
We version only the spec files (under <package name>/SPECS/<package name>.spec) and the patches or some light sources (under <package name>/SOURCES). The source packages of the underlying libraries needs to be downloaded in the SOURCES directory.
Please send patches to the spec files to the email@example.com mailing-list.
In order to actually build, you can then configure %_topdir in your ~/.rpmmacros file to point to where you checked out a package, for example:
%_topdir %(echo $HOME)/dev/rpmbuild %rhel 5 %packager Mathieu Baudier <firstname.lastname@example.org> %dist .el5.argeo
A more persistent alternative is to have the two following files in each package directory:
- <package directory>/rpmrc
include: /usr/lib/rpm/rpmrc macrofiles: /usr/lib/rpm/macros:/usr/lib/rpm/ia32e-linux/macros:/usr/lib/rpm/redhat/macros:/etc/rpm/macros.*:/etc/rpm/macros:/etc/rpm/ia32e-linux/macros:~/.rpmmacros:<package directory>/rpmmacros
(note the ':<package directory>/rpmmacros' appended at the end of the macrofiles line)
- <package directory>/rpmmacros
%_topdir <package directory> %rhel 5 %packager Mathieu Baudier <email@example.com> %dist .el5.argeo
And then call rpmbuild as follow
cd <package directory> rpmbuild --rcfile=rpmrc -ba SPECS/<package name>.spec
These two files are registered in svn:ignore and can typically be automatically generated by scripts or a build framework.
- Original mails suggesting to coordinate EL GIS through OSGeo and describing the rationale and the approach
- On the Live GIS CD mailing-list: http://lists.osgeo.org/pipermail/live-demo/2010-May/001724.html
- On the Discuss mailing list: http://lists.osgeo.org/pipermail/discuss/2010-June/007231.html