how about creating more dependencies to python-libs, ... by adding plugins to core? I think this should be taken in focus of this discussion. IMHO it's not good to add plugins to core that make it necessary to install e.g. mysql with qgis.
Marco Am 15.04.2012 22:55, schrieb Borys Jurgiel: >> This confirms what I've seen in the past: if a core plugin is released via >> a user repository channel, and the user installs it, the installed user >> plugin takes precedence over the core module of the same package name (e.g. >> fTools user plugin is used instead of fTools core plugin). >> >> So, it is my understanding that a core plugin shipping with a release would >> not be 'pinned down' to the QGIS release schedule. > Yes, exactly. You can release a plugin update this way and it mask the one > bundled with Qgis release. If, some day, the user upgrades qgis and the > version of the plugin bundled with master becomes higher that the one > available in the repository, QGIS displays a message to encouage user to > uninstall the update, that is now outdated. > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
