On Fri, Feb 2, 2018 at 3:41 PM, William Kyngesburye <wokl...@kyngchaos.com>
> I still need to figure out the signing. I'll probably do it for v3
> One small hitch I'm thinking about is the separate GDAL Complete - I think
> it would be a bit odd to sign GDAL with a QGIS dev cert, so I am
> considering making a truly all-in-one QGIS, but I really want GDAL as a
> separate package because I use it a lot outside QGIS. There is also the
> external Python 3 that is not signed, which I may also bundle in the QGIS
> app, and additional python modules which are not signed. Though loaded as
> a library to QGIS, I don't know if that matters.
> In the end, even if I make an all-in-one QGIS, I'd still have a separate
> GDAL installer for those that need it, which wouldn't be signed, along with
> my Postgres/PostGIS stack (which uses GDAL Complete), also not signed. So
> many users would still need to fuss with the macOS security to get that
> stuff installed and running.
Shouldn't there be an OSGEO certificate? I remember the discussions but
not the exact resolution.
QGIS-Developer mailing list
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer