"[Bug 844]" <[EMAIL PROTECTED]> writes: > https://qa.mandrakesoft.com/show_bug.cgi?id=844 > > Product: gurpmi > Component: gurpmi > Summary: ?need to run rpm post-install script after choosing > .rpmnew file? > Version: 4.2-6mdk > Platform: All > OS/Version: All > Status: UNCONFIRMED > Severity: minor > Priority: P2 > AssignedTo: [EMAIL PROTECTED] > ReportedBy: [EMAIL PROTECTED] > > > 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".
I think rpm doesn't provide any callback mechanism for doing so, so it's impossible. Even if possible, that would be problematic because when you install a large number of packages, you'd have to decide for .rpmnew files between each package, obliging users to answer the question for the next package to get installed. -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
