[GRASS5] why GPL

[strobe anarkhos]

>
>Strobe, can you explain me in three short sentences why you are not
>able to contribute your code under GPL?
>

Why limit me to three?

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.

I guess that's my problem and not yours. The GPL just clashes with any system where you have lots of interconnected parts 'linked' together instead of using each other's 'files'.

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.

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