> If you really want to check dependencies in your plugin, you could add a > warning for the pages served by the plugin in case a dependency is > disabled, and list the actions to be taken by the administrator to > correct the situation: "Please enable Component2, Component3."
This would basically require all plugin authors to reinvent the wheel everytime they have more complex requirements than what the usual deployment scenarios are. In addition, it would make it less error prone for the administrator, simply clicking on say a given component from a plugin and automatically all the required other components would be enabled as well. But either way, since one has the ability to derive a given environment from a common configuration, basically this is just too much for a light weight system such as trac... Regards Carsten -- Carsten Klein Mobil +491 577 666 256 5 [email protected] axn software UG (haftungsbeschränkt) Wipperfürther Str. 278, 51515 Kürten Geschäftsführung Carsten Klein HRB 66732, Gerichtsstand Amtsgericht Bergisch Gladbach Steuernr. 204/5740/0835, USt-IdNr. DE 266 540 939 Telefon +492 268 801 285, Telefax +492 268 801 285 www.axn-software.de, [email protected] -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
