<p>Apologies for the messy email, I'm on the bus :-p But see below:</p>
<p>> 2012/3/27 Giovanni Manghi <<a href="mailto:giovanni.manghi@gmail.com">giovanni.manghi@gmail.com</a>><br>
>><br>
>> On Tue, 2012-03-27 at 09:51 +0200, G. Allegri wrote:<br>
>> > Ops. How QGis can use GDAL which uses ECW?!<br>
>><br>
>> > 3 - osgeo4w bundles gdal-ecw DLL<br>
>><br>
>> I think there are no erdas libraries in the gdal-ecw package, it is just<br>
>> a "bridge" (sorry if it is not the right term) between gdal and the<br>
>> erdas libraries that the user must get and copy manually in his system.<br>
>><br>
>> cheers<br>
><br>
><br>
> Exactly, the same would happen with an LGPL bridge to ArcPy ;)<br>
><br>
> *Forget Qgis for a moment*<br>
> I create an LGPL library on top of arcpy. Stop<br>
><br>
> Then, I release a GPL plugin for QGis that can import and use the above LGPL library.<br>
> QGis + GPL imports an LGPL library and ONLY USE ITS CODE. The GPL doesn't import arcpy, nor use any proprietary code.</p>
<p>I think the question you have to ask here is this: does your plugin require arcpy to function properly (whether via a bridge or not)? If it doesn't work without it, then its a derivative work*... and since it obviously doesn't work without pyqgis, which is gpl, it can't legally be released as is.</p>
<p>Carson</p>
<p>* I'm not a lawyer, so take what I say with a grain of salt... blah blah...<br>
> <br>
> giovanni<br>
><br>
><br>
>><br>
>> -- Giovanni --<br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Qgis-developer mailing list<br>
> <a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
><br>
</p>