<p dir="ltr">QGIS plugins must me lisenced as GPL, because the depend on QGIS and GPL is viral.<br>
Anyway distributing only .pyc is not advisible, because they assume the same interpreter and the same execution environment that compiled the .pyc bytecode.</p>
<p dir="ltr">giovanni</p>
<div class="gmail_extra"><br><div class="gmail_quote">Il 16 ott 2016 18:12, "Geo DrinX" <<a href="mailto:geodrinx@gmail.com" target="_blank">geodrinx@gmail.com</a>> ha scritto:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Well.  You convinced me.  <br><br><span id="m_-3003586044623889261gmail-result_box" class="m_-3003586044623889261gmail-" lang="en"><span>I have a question.</span> <span>It is possible to deploy</span> <span>a</span> <span>QGIS</span> <span>plugin</span> <span>providing only</span> <span>compiled files</span> <span>through</span> <span>an external</span> <span>repository</span><span>, which</span> <span>is added to the</span> <span>repository</span> <span>list?</span> <span>It is absolutely not</span> <span>my case</span><span>,</span> <span>but I know</span> <span>that someone</span> <span>is doing it.</span><br><span>It is normal</span> <span>or</span> <span class="m_-3003586044623889261gmail-">license</span> <span class="m_-3003586044623889261gmail-">is violated</span></span> ?<br><br></div>Thank you for any info about this.<br><br></div>Roberto<br></div>
<br>______________________________<wbr>_________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a><br>
List info: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br>
Unsubscribe: <a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/qgis-<wbr>developer</a><br></blockquote></div></div>