starting since version 5.0.0 libspatialite supports
Topology and Ground Control Points (GCP).
the first depends on librttopo, that is licensed
under GPL terms.
the second depens on code borrowed from GRASS-GIS
that was initially released under GPL terms.
the net effect is that by enabling one of these
modules (or both) will automatically trigger a
license escalation, and the whole libspatialite
will so implicitly become GPLed (note that this
is nicely allowed by the MPL tri-license).
a GPLed library could easily be far from the ideal
for several users, and after all supporting Topology
and GCP is not necessarily interesting for everyone,
so activating these "special" capabilities was
initially disabled by default in ./configure
./configure --enable-rttopo --enable-gcp
consequently, explicitly enabling this GPLed
modules was required, thus intending an
issues emerging from version 5.0.1
this last version implements full close integration
of libspatialite and librasterlite2, but this
necessarily requires Topology support.
if not, many SQL functions will unexpectedly
fail, thus causing havoc in the testcoverage.
- reverting the default setting for both rttopo
and gcp, so to make --enable-rttopo and
--enable-gcp the default standard option.
in this case a final message will be shown
(as it already happens) informing about
the GPL license escalation.
- users not intending to activate any GPLed
module could still continue to disable them
by explicitily launching
./configure --disable-rttopo --disable-gcp
and in this case a final message will warn
that under such conditions the testcoverage
will become crazy.
your opinions about the opportunity of this change
will be greatly appreciated.