Ejabberd could depend on modules such as pgsql, mysql or odbc. It is therefore better if ejabberd would shutdown before -a database- does. Reproducible: Always
Ejabberd doesn't contains any postgres/mysql flag only has "odbc". Imho valid solution is add "rc_need=postgresql" to /etc/conf.d/ejabberd if your ejabberd uses postgresql. It's rather nothing to do in ebuild.
Maybe I should implement the 'native' pgsql and mysql modules eJabberd can use. It actually uses the odbc interface to configure them. But given the odbc flag, shouldn't this rc_need be there anyway?
With odbc you can connect for many databases or databases which are remote. Even if ejabberd will have native foosql driver it will only needs proper libraries to link against them. We can have database on other host, portage doesn't know about local configuration. It's sysadmin role to prepare start dependencies correctly. If ejabberd could use only one database - foobarsql and it such database would be required by ejjaberd to work then yes, in default conf.d file it should be "rc_need=foobarsql".
Yes, it's impossible to provide all db backends in init script, thus it's better to use provided my Marcin configuration suggestion.
