Request for extending the webapp.eclass aund webapp-config to support plugins. for ex. www-apps/b2evolutin b2evol has plugin support. normally you would add a USE flag for the plugin and install it on request but for b2evol are hundred's of plugins handling them via USE flags isn't a real solution. so my idea is to extend the eclass and config to handle plugins so the main package don't need to be aware of the plugins. for ex. www-apps/b2evolutin-plugin-avatar-0.2.ebuild: webapp_is_plugin_for >=www-apps/b2evolutin-1.10.3 this way the webapp.eclass installs a file into: /usr/share/webapps/b2evolution/1.10.3/plugins/www-apps-b2evolutin-plugin-avatar webapp-config uses this info to handle the plugin install this way it also knows that installing only the plugin wont work. so when b2evolution is installed webapp-config also installs the plugin into the same dir. Reproducible: Always
It's possible to use workaround via INSTALL_DIR: INSTALL_DIR="/roundcube/plugins/sieverules" But this is working clean only for -vhosts installs. With +vhosts you will get an unclean message for the user: "webapp-config -I -h <host> -d roundcube-sieverules roundcube-sieverules 1.16" because of PN in the webapp.eclass: elog " webapp-config -I -h <host> -d ${PN} ${PN} ${PVR}" Isn't is a possible way to apply INSTALL_DIR to such messages by default and to save it for using with webapp-config ?
