I just emerged app-i18n/uim-scim-0.1.3, and I noticed that I have a directory /share/uim which contains files named prime-custom.scm, prime-key-custom.scm, and prime.scm. I find this to be strange - I thought that /share is not a standard root directory according to Linux filesystem convention? If I look in /usr/share/uim (where I expect these files to live), I see that this directory also has three files with the same names, but diff shows that they are substantially different. At least the prim.scm file in /share/uim seem to be older than its counterpart in /usr/share/uim, according to the file headers; for the other files, I can't tell which one is the more current version. If I remove /share/uim, scim-uim seems to work just fine. So this isn't a functionality-breaking bug, but just a minor complaint about the uim package introducing file clutter in the non-standard location /share. I'm sure that this could be made tidy by someone who is familiar with the uim package. Reproducible: Always Steps to Reproduce: 1. emerge app-i18n/uim-scim-0.1.3, which pulls in other packages. 2. look at the files that are deposited in /share/uim 3. ponder the difference with /usr/share/uim
What does `equery belongs /usr/share/uim` say? uim-0.4.7.1 doesn't install those files there, and either app-i18n/uim or app-i18n/prime creates /usr/share/uim. (equery is in gentoolkit)
(In reply to comment #1) > What does `equery belongs /usr/share/uim` say? > uim-0.4.7.1 doesn't install those files there, > and either app-i18n/uim or app-i18n/prime creates > /usr/share/uim. (equery is in gentoolkit) Thanks for investigating this bug report. Here's what I get for one of the files when I run equery belongs on the prime-custom.scm file (the results are the same for prime-key-custom.scm and prime.scm): $ equery belongs /share/uim/prime-custom.scm [ Searching for file(s) /share/uim/prime-custom.scm in *... ] app-i18n/uim-0.4.7 (/share/uim/prime-custom.scm) $ equery belongs /usr/share/uim/prime-custom.scm [ Searching for file(s) /usr/share/uim/prime-custom.scm in *... ] app-i18n/uim-0.4.7 (/usr/share/uim/prime-custom.scm) equery says that both files belong to uim-0.4.7! Strange, isn't it?
Thanks for the feedback. I found what the problem is and fixed it in CVS. (/share/uim gets created if you install uim-0.4.6-r2 or uim-0.4.7 when you don't have app-i18n/prime) If you are unhappy with having that directory, please run `emerge --sync` and remerge uim. Anyhow, I'll unmask uim-0.4.7.1-r1, which is not affected by this bug next week.
