[GRASS5] why GPL

[Jan-Oliver Wagner]

On Mon, Mar 26, 2001 at 06:30:20PM -0800, strobe anarkhos wrote:
> The problem is any form of linking other than linking by hard drive (which for some reason is exempt from the GPL derivative restriction) forces any remote usage of GRASS to adopt the GPL. If I develop an image importer which is used by other applications which allows them to view vector images using the GRASS library I can't do that. My code would have to be GPL because I link to GRASS (or the hypothetical GRASS framework) and only GPL apps could use the importer.

Write a simple converter program and release it under GPL. Inteconnect
your proprietary application e.g. via scripting with the converter and you are
fine. Such interconnection of applications is getting pretty usual.

> I'm not really interested in making code for my own use only and then releasing it as GPL, I mean what's the point? Nobody else could use it.

I still fail to see _your_ point. In all your emails on this list
I see you only argue for another licensing concept for GRASS. Please take a
minute and think about the option to change _your_ licensing concept.

Jan

-- 
Jan-Oliver Wagner               http://intevation.de/~jan/

Intevation GmbH	              	     http://intevation.de/
FreeGIS	                               http://freegis.org/

---------------------------------------- 
If you want to unsubscribe from GRASS Development Team mailing list write to:
minordomo at geog.uni-hannover.de with
subject 'unsubscribe grass5'