Comment 5 for bug 1076975

Sebastien,

I think we need to talk more about how to deal with the transition. In any case 80im-switch needs to be removed or disabled, and after having thought about it, I can't see how it could be safely done in im-switch.

It would be possible to add e.g.

  test -f /usr/bin/im-switch || exit 0

to the top of 80im-switch, update at least Quantal and Precise with im-switch SRUs, wait a couple of weeks, and then accomplish the transition to im-config by re-merging the applicable language-selector changes. However, users who don't upgrade (often enough) would end up with a broken setup.

If "dpkg-maintscript-helper rm_conffile" was used, it would be possible to have specified config files removed when people upgraded to the new im-switch version, but then the automatic launch of an input method would be disabled until the transition to im-config happened. (Maintainer scripts seem not to be run when a package is simply removed.)

The postinst file I proposed may be unconventional, but it would work safely, and would do no harm. Actually, Debian does it in a similar way, i.e. there is a postinst file in im-config that removes 80im-switch. The code is not effective in Ubuntu, though, since md5sum doesn't match.