[GRASSLIST:1024] Re: gdal lib installation problem

[Radim Blazek]

On Monday 25 August 2003 15:44, Frank Warmerdam wrote:
> Radim,
>
> As I understand it we can distribute GRASS with a GPL compatible build
> of GDAL (ie. no GPL incompatible drivers), and then offer for download
> another non-GPL compatible version of GDAL with some extended drivers that
> could be installed over the existing version of GDAL for those willing
> to compromise their freedom to some extent, is that right?  Users who
> do not redistributed GPLed software are allowed to mix in non-GPL
> components.

Yes, this seems to be viable workaround. Absurd license, absurd solution.
We should clarify conditions for such distribution. I think that to build 
- GPL compatible GDAL
- GRASS linked to GPL compatible GDAL
- GPL incompatible GDAL
and distibute all on the same medium or on the same web site sould be OK,
or not?
What about installation, is it legal if installer automaticaly installs 
all components (GPL GDAL, GRASS, replace GPL GDAL by nonGPL GDAL)
in this order? 

> I do however appreciate the importance of not making the basic use of
> GRASS depend on non-free components.

I completely agree, GRASS core must be free, preferably free and not Free,
but possibility to use non-free components is of the same importance.

> In summary, I think it we can work within the requirements of the GPL while
> still offering users that want it extra non-free add-ons for improved
> file import/export capabilities.

Unfortunately import/export is not the only area where proprietary
applications would be desirable. For example, MrSID plugins are freely 
available for ArcView, Microstaion, Mapinfo, etc., why not d.sid for GRASS?
It is not too attractive to tell people, currently using MrSID, that
they can use Free GRASS, but they have to buy 20 new hard drives for data.


Radim