Hi, I saw a bug http://bugs.debian.org/642371 asking for RM by Rolf Leggewie.
This was surprise since Rolf wishes to keep SCIM active for Debian. I think this removal request is mistake by him and he should like to keep this package for having usable SCIM. The critical bug he mention is http://bugs.debian.org/604381 which can be easily fixed by skip building for Qt3 and this is important bug only now. Qt4 support packages are there already so SCIM-BRIDGE provide support for Qt4 needed for squeeze and wheezy. As for dead upstream situation, SCIM-BRIDGE seems to be updated by openSUSE folks quite well. Although Debian package does not have gtk3 support now, SUSE has it. https://build.opensuse.org/package/revisions?package=scim-bridge&project=M17N&showall=1 So it is clear that scim-bridge can be made to support all platforms: gtk+2 gtk+3 qt4. This is nice since this is more robust for C++ ABI change than SCIM's own immodules. Please note SCIM's own immodules are only available as scim-gtk2-immodule. So without scim-bridge, scim does not support Qt4 nor gtk+3 directly. (I know there is a patch for scim-gtk3-immodule. But for unknown reason to me, no one made working updates.) Rolf, I am sure you really meant to keep SCIM for Debian. I think it is wise for you to take package over as much as other related packages. I found this while updating SCIM installation recommendation in im-config package. I think drop building scim-gtk2-immodule and move to scim-bridge seems to be more robust path. After all, move to ibus was driven by the fact SCIM C++ ABI problem. So this may be stable way for you. If I am right, please revert this RM request. Good luck, Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
