Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Even Rouault
Selon Vincent Picavet : > Hi, > > > > The gdal/ecw case is particularly complex, as the ECW licence changes > > > regularly and is some kind of opensource but not really. > > > > The "new" read-only ECW dlls that are distributed in the QGIS Windows > > installer are not at all open source. Paolo

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Vincent Picavet
Hi, > > The gdal/ecw case is particularly complex, as the ECW licence changes > > regularly and is some kind of opensource but not really. > > The "new" read-only ECW dlls that are distributed in the QGIS Windows > installer are not at all open source. Paolo said something not long ago > about

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Alister Hood
> Date: Tue, 27 Mar 2012 11:06:19 +0200 > From: Vincent Picavet > Subject: Re: [Qgis-developer] Re: import proprietary code inside a python > plugin > > Hi, > > > In osgeo4w the gdal-ecw DLLs are released binary compiled. I never needed > > to compile th

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread G. Allegri
2012/3/27 Vincent Picavet > Hi, > > > In osgeo4w the gdal-ecw DLLs are released binary compiled. I never needed > > to compile them by myself. Are you saying that osgeo4w is doing something > > incorrect? > > The gdal/ecw case is particularly complex, as the ECW licence changes > regularly and is

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Jürgen E . Fischer
Hi Giovanni, On Tue, 27. Mar 2012 at 09:51:52 +0200, G. Allegri wrote: >Ops. How QGis can use GDAL which uses ECW?! >1 - GDAL is LGPL I think I saw that a couple of time in this thread already. GDAL is not LGPL, it is X/MIT. More relaxed - you can do just about anything with it - includi

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Vincent Picavet
Hi, > In osgeo4w the gdal-ecw DLLs are released binary compiled. I never needed > to compile them by myself. Are you saying that osgeo4w is doing something > incorrect? The gdal/ecw case is particularly complex, as the ECW licence changes regularly and is some kind of opensource but not really.

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Carson Farmer
Apologies for the messy email, I'm on the bus :-p But see below: > 2012/3/27 Giovanni Manghi >> >> On Tue, 2012-03-27 at 09:51 +0200, G. Allegri wrote: >> > Ops. How QGis can use GDAL which uses ECW?! >> >> > 3 - osgeo4w bundles gdal-ecw DLL >> >> I think there are no erdas libraries in the gdal-

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread G. Allegri
2012/3/27 Giovanni Manghi > On Tue, 2012-03-27 at 09:51 +0200, G. Allegri wrote: > > Ops. How QGis can use GDAL which uses ECW?! > > > 3 - osgeo4w bundles gdal-ecw DLL > > I think there are no erdas libraries in the gdal-ecw package, it is just > a "bridge" (sorry if it is not the right term) bet

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Giovanni Manghi
On Tue, 2012-03-27 at 09:51 +0200, G. Allegri wrote: > Ops. How QGis can use GDAL which uses ECW?! > 3 - osgeo4w bundles gdal-ecw DLL I think there are no erdas libraries in the gdal-ecw package, it is just a "bridge" (sorry if it is not the right term) between gdal and the erdas libraries that t

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread G. Allegri
Ops. How QGis can use GDAL which uses ECW?! 1 - GDAL is LGPL 2 - it's imported by QGis, so it doesn't use QGis but is used by... 3 - osgeo4w bundles gdal-ecw DLL giovanni 2012/3/27 Noli Sicad > QGis (GPL) + GPL + LGPL + proprietary = illegal. > > Any proprietary code added to GPL is illegal. U

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread G. Allegri
2012/3/27 Paolo Corti > On Tue, Mar 27, 2012 at 9:07 AM, G. Allegri wrote: > > I premit that I've already chosen a solution to bypass these issues: one, > > common library and two plugins, one for qgis and one for arcpy. The > plugins > > will interact through pickling, sharing a common data str

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Noli Sicad
QGis (GPL) + GPL + LGPL + proprietary = illegal. Any proprietary code added to GPL is illegal. Unless they re license the code as LGPL. Noli On 3/27/12, Paolo Corti wrote: > On Tue, Mar 27, 2012 at 9:07 AM, G. Allegri wrote: >> I premit that I've already chosen a solution to bypass these iss

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread Paolo Corti
On Tue, Mar 27, 2012 at 9:07 AM, G. Allegri wrote: > I premit that I've already chosen a solution to bypass these issues: one, > common library and two plugins, one for qgis and one for arcpy. The plugins > will interact through pickling, sharing a common data structure from the > common library.

Re: [Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-27 Thread G. Allegri
I premit that I've already chosen a solution to bypass these issues: one, common library and two plugins, one for qgis and one for arcpy. The plugins will interact through pickling, sharing a common data structure from the common library. This is the easiest solution for me to deploy (no servers as

[Qgis-developer] Re: import proprietary code inside a python plugin

2012-03-26 Thread Alister Hood
> Message: 4 > Date: Mon, 26 Mar 2012 13:33:54 +0200 > From: Tim Sutton > > > I personnaly consider that libraries should not be under a GPL licence > but a > > LGPL one, which keeps the opensource aspect while facilitating mixing > with > > other softwares. GPL is fine with end user software bui