http://qa.mandrakesoft.com/show_bug.cgi?id=844
------- Additional Comments From [EMAIL PROTECTED] 2003-03-15 19:32 ------- Of course, one could query the scripts from the package *after* they have been installed, and run them again? But the question is whether all %post scripts would be safe? And trigger scripts would make this more difficult. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: If a package is installed via rpmdrake, and a config file is changed, so that a .rpmnew file is created, the user is prompted (I think by gurpmi?) with the option to use the .rpmnew file, the original, and to compare differences. This is really nice. But the rpm is alerady installed at that point. If the rpm had to run programs after installation - e.g. a server, or generate fils - this was done using the old config file. Example - if /etc/fonts/fonts.conf changes in an update, the font cache will be rebuilt using the old /etc/fonts/fonts..conf before the user is prompted, and after selecting .rpmnew the font cache and the conf file are out of sync, possibly causing slow startup or incorrect behaviour for some programs. There are other examples of course, e.g. if apache.conf is changed. I'm wondering if it'd be possible to integrate rpm & gurpmi a little further, and have the rpm post-install stuff done *after* the user has decided? Or if this even makes sense? Just a thought, I've marked it "minor".
