Now that phpMyAdmin provides config.inc.php for overrides of config.default.php it would seem sensible to handle config in the following manner: 1) Allow updates to overwrite config.default.php so that new defaults come into operation automatically. 2) Write the mysql user and password information to config.inc.php (see later comment). 3) Mark config.inc.php as a webapp-config config file and preserve existing state. Is it necessary to regenerate the mysql user and password information at each emerge? Under this new scheme I envisage that it would only need to be done if config.inc.php doesn't already exist.
(In reply to comment #0) Thanks for your comments. > 1) Allow updates to overwrite config.default.php so that new defaults come > into operation automatically. I'd rather keep things as-is for the time being, on the off-chance that some users edit config.default.php directly. I don't think running dispatch-conf is a huge inconvenience :) > 2) Write the mysql user and password information to config.inc.php (see later > comment). I think it makes more sense to leave it in config.default.php, as any local changes in config.inc.php will take precedence. Also see below. > 3) Mark config.inc.php as a webapp-config config file and preserve existing > state. The ebuild doesn't install config.inc.php at all, so the local file will not be overwritten. No need to mark it as a config file. > Is it necessary to regenerate the mysql user and password information at each > emerge? Under this new scheme I envisage that it would only need to be done if > config.inc.php doesn't already exist. Good point. I've updated the postinstall instructions to suggest that the first step only needs to be done when installing phpmyadmin for the first time. Feel free to reopen if you feel I'm missing something.