<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
I just reviews archeos-gis metapackage. Here is a fast reposrt:<br>
Main question:<br>
<br>
1. Which version of <span>GRASS</span> <span>GIS</span> should we
provide?<br>
2. Should we go on in keeping OpenJUMP in ArcheOS?<br>
3. Spatialite-<span>GIS</span> is really necessary?<br>
OpenJUMP and Spatialite-<span>GIS</span> should be packaged
<p>Changelog: Up to now there are no changes in this session (<span>SAGA</span>
and uDIG are dismissed since ArcheOS Theodoric).<br>
</p>
<p>My personal considerations:<br>
</p>
<p>1. the stable version of GRASS is 7, we should provide this
version (I tested it for a long time in ArcheOS Theodoric and
everything workd fine). There is no package in Jessie for it. A
fast solution could be a backport from stretch (testing). GRASS 7
is considered the stable release by GRASS developer team. What do
you think about it @Fabrizio? The backport could work? <br>
</p>
<p>2. Thanks to the good drawing vector tool of QGIS (in the last
version), OpenJUMP is no more mandatory IMHO. We just have a small
bug: Polygontool (<a class="moz-txt-link-freetext" href="https://github.com/keulemaster/Polygontool">https://github.com/keulemaster/Polygontool</a>), a
tool that can spare days (month?) of work inbig field survay
campaign just export format for openjump. Other tool (e.g. in QGIS
or gvSIG can do almost the same things, but not everything). I
guess we should test better these tools on a big survey campaign
and later choose</p>
<p>3. I think that sooner or later QGIS will also be able to handle
sqlite and spatialite data in a better way. We could consider this
software as optional by now.<br>
</p>
<p>Anyway both OpenJUMp and Spatialite-GIS were packaged for
ArcheOS-Theodoric. we could see if it is not too difficult to
migrate these packages to archeos-next.<br>
<a class="resultlink"
href="https://packages.debian.org/stretch/grass"></a></p>
<br>
</body>
</html>