[packaging question] multilib gtkimm (Input Method modules)

Jens Petersen petersen at redhat.com
Sat Apr 29 06:18:44 UTC 2006


Hi,

Is there some way to encourage yum and pirut to always install 
scim-libs.i386 too on x86_64 when scim-libs.x86_64 gets installed?

ie if I do "yum install scim-anthy" or "yum groupinstall 
japanese-support" on x86_64, I want it to install scim-libs.i386 as 
well as scim-libs.x86_64 (a dependency of scim-anthy), just as happens 
when installing with anaconda.

The context [1] for this question is users of 32bit apps on x86_64 
complaining that IM doesn't work for them and it is not at all obvious 
that this is due to scim-libs.i386 not being installed.

My initial idea for a solution was to add something like:

  # require 32bit gtk IM module for 64bit multilib arches
  %ifarch x86_64 s390x
  Requires: %{_prefix}/lib/gtk-2.0/immodules/im-scim.so
  %endif

to the main scim package, so that installing scim.x86_64 would pull in
scim-libs.i386.

Is there a better to deal with this?  Can something be added to 
comps.xml to help?

Jens

[1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=188398

ps Another side of the problem is that gtk2 doesn't behave very well 
when asked to use an IM module that is not available: eg if 
GTK_IM_MODULE is set to "scim", scim-libs.x86_64 is installed, and 
scim-libs.i386 not installed, then 64bit gtk apps will be fine, but IM 
will behave quite strangely on 32bit apps.  In this case it would be 
better if gtk tried to fallback to XIM say IMHO (I believe qtimm does 
this).  In this sense relying on /etc/gtk-2.0/*/gtk.immodules would be 
safer, but we really need a more reliable way than that to choose 
which immodule is used by default.




More information about the Fedora-maintainers mailing list