a new key
This change moves the old "app/plugin_installer/checkOnStart" setting
key to a new "plugins/automatically-check-for-updates" key, and
switches the default value to enable automatic checks
This is designed to switch all existing QGIS users to the new
default behavior of checking for plugin updates at startup (at
a maximum of once every 3 days).
It is intended to offer a better QGIS experience to our users,
by proactively informing all users when plugins should be
updated, ensuring that ALL users are more likely to upgrade
plugins and get the bug fixes for plugins promptly.
Enterprise users who have customised this setting in their
deployments will need to adapt their scripts for the new
setting key.
instead of manually
Too many QGIS users use outdated plugins without even realising it,
leading to an overall buggier QGIS experience then they should have...
* [cmake] generalize Python output directory in UseTest macro
this is helpful in case we set up another python output directory (eg PySide2)
* define python output directories to the parent scope
* try with target_include_directories
* define vars on top level
* Update UsePythonTest.cmake
* some cleanup
* more cleanup
* fix uic
* fix path for all platforms
* fix var
2021-05-13 07:32:03 +02:00
Benjamin Jakimow benjamin.jakimow@geo.hu-berlin.de
manually in the plugin manager, then force a reload of the repositories
and don't rely on cached copies of the repo manifest
Otherwise it's not possible to force a refresh on certain types of
plugin repositories where it's not possible to modify the Cache-Control
attribute of the repo
Note that to avoid unnecessary server load, we still use cached
copies during startup and by default. It's only when a user explicitly
hits the "Reload all repositories" button that we force a non-cached
fetch.
Fixes#34351
Implementation of QEP 132:
Manage python cross-plugins dependencies
A new optional metadata entry will be added to metadata.txt: plugin_dependencies
The metadata will contain a comma separated list of plugin names, with a format similar
of the one used by pip, with optional version.
After a successful plugin installation, if the plugin has any unsatisfied dependency,
a dialog will pop-up with the list of unmet dependencies and the user
will be able to choose if she wants to install or upgrade the
dependencies or ignore them.
Example metadata:
plugin_dependencies = QuickMapServices==0.19.10.1,QuickWKT
Funded by GISCE-TI S.L.
