Custom Query (1118 matches)

• The most easy port is the Marble-Qt port which provides all features. This could be used as a base:

​https://launchpad.net/ubuntu/trusty/i386/marble-qt/4:4.12.0-0ubuntu1

• all languages should be packaged. For the Qt-Only version this requires special treatment to get the .qm files generated and packaged
• gps support should be included
• Ideally it would be nice if Marble's shapelib support would get enabled. This requires to set the LIBSHP_INCLUDE_DIR with cmake so that Marble will find the shapelib.
• Integrating Quazip support in addition would provide support for .kmz files (without that Marble can only display uncompressed kml files).

As we have a number of people collaborating in the building of the Virtual Machine, and as Virtual Machines are very large and slow and costly to download, we need a way that people can synchronise with the latest image without download 3 meg of data.

I propose that we set up the following:

• Mount the GISVM somewhere, probably on download.osgeo.org. (Ricardo has some other ideas for hosting locations which I can't put my finger on as I type this).

• Set up a configured rsync client inside GISVM image, probably using Unison, This will provide read only access to the master Virtual Machine. This will allow everyone to sync their local images with the latest.

• Set up the master GISVM image with read only access for most people, maybe through an anonymous password or similar.

• Set up write access to the GISVM image to the core GISVM team, probably only one or 2 people, who will be responsible for running people's scripts, and then uploaded the changed image back onto the master image.

• Periodically, this master image will be copied into a specific release with a version number.

Since the documents are now hosted under git (and mirrored on GitHub) we can take advantage of the Travis continuous integration capabilities and catch any build errors before merging new code.