Regarding the presence of binaries, I think there are three points : 1. why to preclude the presence of them? Security? Transparency?
If the point is the former, are we implying that the rest of the code will be inspected against malicious code? If the latter, isn't it enough to require the source code to be provided as well? 2. Doesn't this create an unnecessary hardship for small developers? 3. Are we risking to move back to a "many repositories" environment? Cheers, Pedro On 19 Dec 2016 1:01 PM, <qgis-developer-requ...@lists.osgeo.org> wrote: > Send Qgis-developer mailing list submissions to > qgis-developer@lists.osgeo.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.osgeo.org/mailman/listinfo/qgis-developer > or, via email, send a message with subject or body 'help' to > qgis-developer-requ...@lists.osgeo.org > > You can reach the person managing the list at > qgis-developer-ow...@lists.osgeo.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Qgis-developer digest..." > > > Today's Topics: > > 1. Plugin [1152] QgisODK unapproval notification. (nore...@qgis.org) > 2. Re: Plugin [1102] AequilibraE approval notification. > (Matthias Kuhn) > 3. Plugin [1148] Potential Slope Failure approval notification. > (nore...@qgis.org) > 4. Re: Fwd: [Qt5] Compilation problems on windows (alisovenko) > 5. Re: Plugin [1102] AequilibraE approval notification. > (Pedro Venâncio) > 6. Travis failure after introducing spell-checking (Alexander Bruy) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 19 Dec 2016 14:40:14 -0000 > From: nore...@qgis.org > To: enrico...@gmail.com, qgis-developer@lists.osgeo.org > Subject: [Qgis-developer] Plugin [1152] QgisODK unapproval > notification. > Message-ID: <20161219144014.16754.62883@320558c5528b> > Content-Type: text/plain; charset="utf-8" > > > Plugin QgisODK unapproval by pcav. > The plugin version "[1152] QgisODK 1.0" is now unapproved > Link: http://plugins.qgis.org/plugins/QgisODK/ > > > ------------------------------ > > Message: 2 > Date: Mon, 19 Dec 2016 16:00:21 +0100 > From: Matthias Kuhn <matth...@opengis.ch> > To: Alessandro Pasotti <apaso...@gmail.com>, Luigi Pirelli > <lui...@gmail.com> > Cc: "qgis-developer@lists.osgeo.org" <qgis-developer@lists.osgeo.org>, > Pedro Camargo <veigacama...@gmail.com> > Subject: Re: [Qgis-developer] Plugin [1102] AequilibraE approval > notification. > Message-ID: <a143144b-e687-c1b4-ae2e-838e1566f...@opengis.ch> > Content-Type: text/plain; charset=utf-8 > > On 12/19/2016 03:33 PM, Alessandro Pasotti wrote: > > On Mon, Dec 19, 2016 at 3:26 PM, Luigi Pirelli <lui...@gmail.com > > <mailto:lui...@gmail.com>> wrote: > > > > Hi Alessandro > > > > this can be radical, but has the positive effect to introduce a "best > > practice" to develop plugins with external binary dependencies... I > > would agree, but what else respect that plugins that now have already > > binaries and were accepted? Should be modified! > > > > Last case from some minutes ago is this just approved plugin with a > > jar included > > https://github.com/enricofer/QgisODK/tree/master/pyxform/ > odk_validate <https://github.com/enricofer/QgisODK/tree/master/pyxform/ > odk_validate> > > that came from a nother external foss project. > > > > Because everyone have to modify it's plugin to move to qgis3 => we > > could leave proposal 1) for 2.x and proposal 2) for qgis3.0 giving > > time to adapt the plugin to downloading binary from external repo. > > > > cheers > > Luigi Pirelli > > > > > > > > I've just checked on the plugins site where somebody (I believe Paolo) > > wrote a policy: > > > > ... > > does not contain architecture-dependant binaries > > ... > > ... which in the two cases here (cython and java) shouldn't be triggered > because both are architecture independent. > > > > > > > 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. > > If that doesn't sound like a good idea, I'm not sure it's better to > prefer a (silent) download of "some binaries" from "somewhere" in the net. > Just for reference, as far as I know, python wheels also allows > uploading pre-compiled binaries to their repo. > But I might also just be missing the point. > > Matthias > > > ------------------------------ > > Message: 3 > Date: Mon, 19 Dec 2016 15:55:32 -0000 > From: nore...@qgis.org > To: fredr...@gvc.gu.se, qgis-developer@lists.osgeo.org > Subject: [Qgis-developer] Plugin [1148] Potential Slope Failure > approval notification. > Message-ID: <20161219155532.16753.73273@320558c5528b> > Content-Type: text/plain; charset="utf-8" > > > Plugin Potential Slope Failure approval by pcav. > The plugin version "[1148] Potential Slope Failure 0.3 Experimental" is > now approved > Link: http://plugins.qgis.org/plugins/PotentialSlopeFailure/ > > > ------------------------------ > > Message: 4 > Date: Mon, 19 Dec 2016 10:42:11 -0700 (MST) > From: alisovenko <alexander.lisove...@gmail.com> > To: qgis-developer@lists.osgeo.org > Subject: Re: [Qgis-developer] Fwd: [Qt5] Compilation problems on > windows > Message-ID: <1482169331462-5300521.p...@n6.nabble.com> > Content-Type: text/plain; charset=us-ascii > > Hi! > I have a similar problem. > I try to build master qgis with qt 7.5.1 (windows 10 msvc 2013 and 2015). > But have Multiple errors and can not to build qgis: > > qgis_core.lib(qgis_core.dll) : error LNK2005: "public: __thiscall > QVector<class QVariant>::QVector<class QVariant>(class QVector<class > QVariant> const &)" already defined in qgsgraph.obj [...] > sgraph.obj > [E:\dev\nextgis.qgis\qgis-master-build\src\analysis\qgis_analysis.vcxproj] > qgis_core.lib(qgis_core.dll) : error LNK2005: "public: __thiscall > QVector<class QVariant>::~QVector<class QVariant>(void)" > (??1?$QVector@VQVariant@@@@QAE@XZ already defined in qgsgraph.obj [...] > qgis_core.lib(qgis_core.dll) : error LNK2005: "public: class QVector<class > QVariant> & __thiscall QVector<class QVariant>::operator=(class > QVector<class QVariant> const &)" (??4?$QVector@VQVariant@@@@QAEAAV0@ABV0@ > @Z) already defined in qgsgraph.obj [...] > qgis_core.lib(qgis_core.dll) : error LNK2005: "public: __thiscall > QVector<class QVariant>::QVector<class QVariant>(void)" > (??0?$QVector@VQVariant@@@@QAE@XZ) already defined in qgsgraph.obj [...] > > Maybe you know how to get rid of the error? > > > > > -- > View this message in context: http://osgeo-org.1560.x6.nabble.com/Fwd-Qt5- > Compilation-problems-on-windows-tp5295744p5300521.html > Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. > > > ------------------------------ > > Message: 5 > Date: Mon, 19 Dec 2016 17:44:33 +0000 > From: Pedro Venâncio <pedrongvenan...@gmail.com> > To: "qgis-developer@lists.osgeo.org" <qgis-developer@lists.osgeo.org> > Subject: Re: [Qgis-developer] Plugin [1102] AequilibraE approval > notification. > Message-ID: > <CAMCJChsi4CUhzVZ5f7bE_4R+-RPvMDKwba4asJVXNB=uQ12ZNw@ > mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.osgeo.org/pipermail/qgis-developer/ > attachments/20161219/37e4b3b3/attachment-0001.html> > > ------------------------------ > > Message: 6 > Date: Mon, 19 Dec 2016 21:07:09 +0200 > From: Alexander Bruy <alexander.b...@gmail.com> > To: Qgis Developer List <qgis-developer@lists.osgeo.org> > Subject: [Qgis-developer] Travis failure after introducing > spell-checking > Message-ID: > <CALuHMPB69MUvHZ-nGASwZukh3RNs7HR9uAoo5=2DnVsn2 > vl...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi all, > > looks like recently introduced spell-checking on Travis leads to > reporting failures > even if there are no build errors and all tests passed. This happens > with PR which > delete files, see for example > https://travis-ci.org/qgis/QGIS/builds/184481431#L1400 or > https://travis-ci.org/qgis/QGIS/builds/185214040#L1401 > > -- > Alexander Bruy > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > > ------------------------------ > > End of Qgis-developer Digest, Vol 134, Issue 58 > *********************************************** >
_______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
