Keep in mind it is only a problem if you plan on distributing your
plugin... if it is just for internal use then I wouldn't worry about
it :-p
C
On Mon, Mar 26, 2012 at 11:45 AM, G. Allegri gioha...@gmail.com wrote:
I had to create a python plugin to obatin some interactions with the ESRI
2012/3/26 Carson Farmer carson.far...@gmail.com
Keep in mind it is only a problem if you plan on distributing your
plugin... if it is just for internal use then I wouldn't worry about
it :-p
Well, it's for a customer, so it could be an issue...
I totally respect the choice of the developers
Hi
On Mon, Mar 26, 2012 at 4:52 PM, G. Allegri gioha...@gmail.com wrote:
Through the various considerations on this topic there are two positions the
seems contradictory to me:
I did some research on this, and the conclusion is that import is
functionally and legally equivalent to linking
Ah, Tim, it's getting clear. Thanks.
The key point is distribution, as always with GPL.
In my case I won't distribute the ESRI geoprocessing libraries, they're
part of the ArcGIS distribution, which is only availbale to users having it
installed on they're computers.
The import satement will
Hi,
Le lundi 26 mars 2012 21:32:31, G. Allegri a écrit :
Ah, Tim, it's getting clear. Thanks.
The key point is distribution, as always with GPL.
In my case I won't distribute the ESRI geoprocessing libraries, they're
part of the ArcGIS distribution, which is only availbale to users having it
Ok, going through hyopthesis things are getting clear:
my plugin is ok until it doesn't load something proprietary in its process
space. As soon as it happens I must be able to provide the source of every
code running in the same process. Right?
giovanni
2012/3/26 Vincent Picavet
Hi,
Ok, going through hyopthesis things are getting clear:
my plugin is ok until it doesn't load something proprietary in its process
space. As soon as it happens I must be able to provide the source of every
code running in the same process. Right?
Right.
Importing esri python module falls
Perfect. I find thinking in the terms of process space a clear criterior.
This makes dynamic and static linking equivalent...
So, going back to SEXTANTE, it can be given an LGPL license but it cannot
use non-free code when used through Qgis, while it's free to do it when
used through, e.g.,
QGIS + QGIS plugin (GPL) - data - Arcpy script (LGPL, MIT, BSD)
Yes it's ok as long as they don't directly import each other.
Thanks,
Alex
On 03/26/2012 03:07 PM, Noli Sicad wrote:
QGIS + QGIS plugin (GPL) + Arcpy script (LGPL, MIT, BSD) = might be OK.
Noli
On 3/27/12, G. Allegri
