An emerge -u world can course a lose of user data stored in 'config.inc.php' Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Actual Results: http://lists.mushaake.org/pipermail/php/Week-of-Mon-20040315/007393.html
pkg_postinst() { einfo einfo "To complete installation, you must" einfo "1. Update your configuration files:" einfo " etc-update" einfo "2. Update MySQL's grant tables and the pmadb database:" einfo " ebuild /var/db/pkg/${CATEGORY}/${PF}/${PF}.ebuild config" einfo "3. Reload MySQL:" einfo " /etc/init.d/mysql restart" einfo einfo "If you are upgrading from an earlier version and are using phpMyA dmin's" einfo "features for master/foreign tables be sure to read" einfo " http://localhost/phpmyadmin/Documentation.html#col_com" einfo "You will need to perform the ALTER TABLE step yourself." einfo einfo "Finally, point your browser to http://localhost/phpmyadmin/." einfo } pkg_config() { einfo "This will execute the contents of ${ROOT}etc/phpmyadmin/mysql-set up.sql" einfo "Type in your MySQL root password:" mysql -u root -p < ${ROOT}etc/phpmyadmin/mysql-setup.sql || die einfo "You need to reload MySQL for the changes to take effect" } how about reading the einfo msgs ?
Not having such files overwritten is what gentoo's config-file-protection is all about, I don't see why it isn't used here. Maybe this is rather a feature-request than a real bug, but not having to reconfigure PHPMyAdmin after every update is a valid request IMHO.
This won't be a problem once phpmyadmin's ebuild uses the new webapp-config approach. webapp-config provides CONFIG_PROTECT behaviour for the configuration files of web-based applications. Best regards, Stu
