<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7638.1">
<TITLE>[postgis-users] A PostGIS-Raster data proposal</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>> GDAL manages the Kakadu issue by simply providing an adapter and leaving the<BR>
> acquisition of the source up to the installer; why would this not work<BR>
> equally well for postGIS ?<BR>
PostGIS has a GPL license which basically says that the source code of packages linked to it must also be covered by the GPL. Kakadu has a conflicting license, so you put the two packages together in the same executable, you either have to honor the GPL and violate the Kakadu license, or vice versa. Neither option is legally valid.<BR>
<BR>
GDAL is distributed under the MIT license, which does not put any requirements other packages that might be linked in the same executable with GDAL. Thus you can link optional closed-source packages to GDAL.</FONT></P>
</BODY>
</HTML>