On Tue, Apr 17, 2007 at 01:19:25PM +0200, Loïc Minier wrote: > On Tue, Apr 17, 2007, Ming Hua wrote: > > I've prepared a new upload for scim that is compatible with the new GTK+ > > ABI and sent it to my sponsor, so this bug should be fixed soon. > > (Let me know if you need sponsoring.)
It has be uploaded, but your offer is still appreciated. > > Also the scim package has the same problem as gcin package, i.e., > > hardcoding the /usr/lib/gtk-2.0/2.10.0/ directory. In scim this is > > done in quite a few different places, and as I don't know much about > > autotools, hardcoding is the easiest way for me. If you think this is > > very bad practice and can provide a patch, I'd be very happy to fix it. > > Yes; the hardcoding comes from a Debian specific patch, but the > upstream configure already defines "GTK_BINARY_VERSION", so it's not > too intrusive to change. I'm attaching you the updated patches and > interdiff which I hacked starting from 1.4.4-7 (unstable), but it > should apply to your SVN I suppose. I also fixed debian/rules and > debian/scim-gtk2-immodule.install again here. Thanks a lot for this quick and nice patch! I now have a good idea about what should be done here to get rid of the hardcoding. As there has been a new upstream release and I plan to do a new upload soon, I'll incorporate your patch on the new upstream upload. > Could you try to bring this patch upstream? Upstream should be > installing in the ABI dependent dir anyway, otherwise their modules may > break silently when the IM Module ABI changes. Upstream is aware of this issue. And IIRC there was discussion about this but I forgot the details. I'll see what I can do. Ming 2007.04.19
