On Mon, Jul 16, 2007 at 10:21:54AM +0200, Corinna Vinschen wrote: >On Jul 13 13:06, Corinna Vinschen wrote: >> On Jul 13 05:58, Andrew Schulman wrote: >> > I think that this won't be necessary if we use Dave's suggestion to remove >> > config files in preremove scripts if they haven't changed. Then all the >> > postinstall script has to do is >> > >> > if [ -f /etc/file ] ; then >> > exit 32 >> > else >> > cp /etc/defaults/etc/file /etc >> > fi >> > >> > (but with smarter exit handling). >> >> Hmm, yes, that doesn't sound bad. >> >> > How about both: postinstall scripts that weren't able to update a config >> > file because it was modified exit with signal 32 (or whatever; I suggest a >> > power of 2 so we can use bitmasks). If any postinstall scripts exit with >> > 32, then setup searches for .cygnew files in /etc and presents the list to >> > the user. A side effect of this would be that each time a config file >> > can't be updated, setup would present the entire list of .cygnew files to >> > the user-- even if they were there from a previous installation, so the >> > user had already been notified about them before. I think this would >> > probably be okay, maybe even good, as long as the user didn't get a new nag >> > screen *every* time they installed any new package-- only when a config >> > file couldn't be updated. >> >> I agree. > >Any comment from our setup gurus?
I have no comment other than to note that you can't "exit with signal 32". You can "exit 32" but you can't "kill -32 $$". cgf
