Home_greyopenFATE - openSUSE feature tracking > #313546
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Get rid of SuSEconfig.scim

Feature state

openSUSE Distribution
Done

Description

There is no point to run that code after installation of every package (and it's not run when you use zypper or 3rd party tools anyways). That code should be only run as a part of post-install of affected packages.

Relations

Testcase

https://build.suse.de/package/show/home:okir:QA/qa_test_removefiles

Discussion


icons/user_comment.png T. I. wrote: (5 years ago)

SCIM should be simply replaced with the new framework, e.g. IBUS. Keeping SCIM in SLE12 is a heavy maintenance load.

If we go for IBUS, rather the question is how to migrate seamlessly.

icons/user_comment.png J. Z. wrote: (5 years ago)

I am OK with replacing SCIM with other new framework and saw lots of discussion in the maillist. But I would like to confirm that if IBUS can provide as much as what SCIM provide for different languages inputting. As I can see, there should be no problem for Asian language to use IBUS, but not sure if there is any problem for European Languages. (This may need some help from European colleagues to confirm, I guess?)
Also Takashi, would you be able to guide Fan Jun to do the replacement? He may not be very familiar with our SUSE scripts and configuration locations. To make it seamlessly, I think your help is highly appreciated!

BTW, I see some requests from community to use fcitx instead of ibus, so I think we also need to evaluate this too to avoid too frequent changes for input framework, which will not confuse our customer too much and make our lives much easier. :)

icons/user_comment.png D. L. wrote: (4 years ago)

SLE12 uses IBUS, so this fate is not so important. But still, SuSEconfig.scim should be remove in our factory.

Assign to Yang Tao for his new employee training..

icons/user_comment.png T. Y. wrote: (4 years ago)

I checked the SCIM.spec file and found that the SuSEconfig.scim file will be executed in the %Post procedure.
What SuSEconfig file do is:
1.Create a configuration file named "global" underneath the /etc/scim directory.
2.Check what is the default system keyboard setting,and write it into the "global"
I think "global" will only be read when the SCIM program starts,for its inner configuration.

Since yast will not execute the SuSEconfig.scim,I think we can just close this fate

icons/user_comment.png A. J. wrote: (4 years ago)

Please rename the file to something better, having it names SuSEconfig will confuse people as you see with this discussion. With the rename done, I agree with your assessment that this can be closed.

icons/user_comment.png T. Y. wrote: (3 years ago)

File SuSEconfig.scim was renamed into scim.config in request 32561 on build.suse.de. And another request with same changes will be submit on opensuse,too
Thanks

icons/user_comment.png F. C. wrote: (3 years ago)

fixed also on openSUSE

Last change: 3 years ago
Voting
Score: -1
  • Negative: 1
  • Neutral: 1
  • Positive: 0
Tags
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint