I wasn't aware to have an executable between my plugin sources. In my case I have just removed it from the pyxform library as QgisODK plugin does not require XForm validation and resubmit it to the repository. But I think that if a library has an open source origin, a corresponding licence, and is shared with a community should be normally accepted in a qgis plugin bundle even if containing compiled binaries. We have to think that gis is computationally intensive and a software like QGis is suited to integrate different tools. So I think that is not so useful for QGis users to strictly fulfil the "no executable" policy. Protecting in this way QGis global stability we could lose many opportunities, leaving them to proprietary systems much more uninhibited.
Best Regards Enrico Ferreguti 2016-12-19 18:44 GMT+01:00 Pedro Venâncio <[email protected]>: > Hi, > > > >> As I said, I'm in favour of a source-only policy, there are easy >> technical solutions to download binaries after installation if a plugin >> requires them and hosting on our plugin site binary blobs that we cannot >> inspect doesn't look a good idea to me. >> >> >> > Crayfish plugin uses this approach http://www.lutraconsulting.co. > uk/products/crayfish/wiki > > It download the binary libraries when installing the plugin from QGIS > repository. > > Best regards, > Pedro > > > > _______________________________________________ > Qgis-developer mailing list > [email protected] > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
