[Qgis-developer] Plugin [1102] AequilibraE approval notification.

[Luigi Pirelli]

Hi Enrico,

the fact that you weren't aware of a binary in your plugin give me
more reasons to propose an restrictive approach! I agree with you that
in some cases have binaries is a necessity, btw it's not complex to
design the plugin with a setup step.
I agree with Enrico and I continue thinking that we can have a loose
but explicit control by the user documenting any binary available in
the plugin (solution 1).

regards
Luigi Pirelli

**************************************************************************************************
* Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com
* LinkedIn: https://www.linkedin.com/in/luigipirelli
* Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli
* GitHub: https://github.com/luipir
* Mastering QGIS 2nd Edition:
* https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition
**************************************************************************************************


On 19 December 2016 at 21:47, Enrico Ferreguti <enricofer at gmail.com> wrote:
> 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 <pedrongvenancio at gmail.com>:
>>
>> 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
>> Qgis-developer at lists.osgeo.org
>> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
>
>
>
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer
> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer