Hi, The problem already happened when I developed processing plugins (which depend on processing), now it happens because I'm developing a complex plugin with some parts that will be useful as independent plugins (so I developed them as plugins): there is no clean way that I know about to specify dependencies and inform the user when they are not available.
It would be nice if the plugin manager could use a list of dependencies to activate several plugins at a time. The same mechanism could also be used to test if non-standard dependencies required by a plugin are available. It could be in metadata.txt, or, even better, in requirements.txt, what do you think ? V. _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
