Hi, (I am surprised...) I think we may have some misunderstandings.
I am not saying that gtk-query-immodules is normally run automatically by maintainer script. I agree that is the most popular usage. You seems to dismiss this bug report based on this fact only. But if you carefully read my previous postings excluding some minor deficiencies, you can see that there were occasions when this command was used to list installed immodules for checking system configuration by the user per request of upstream package maintainer of IM system as I reported. Debian does not put symlink of this command in $PATH. If you are dismissing me stating my reported usage case is pedantically awkward corner case, it makes some sense. But your message was strange to me. Since this is a minor bug, I do not insist more. But I post here for the record to make sure there remains no misunderstandings. Osamu On Thu, Jan 31, 2013 at 06:22:55PM +0100, Michael Biebl wrote: > I've talked to Joss and we agreed this is not actually a bug, so I'm > going to close those two bug reports. > gtk-query-immodules produces a cache file in an architecture specific > location, I have no argument against this tool is mostly used for that usage. > that's why it was move to multi-arch paths, too. > It's dpkg triggered, so it is automatically run whenever an immodule is > installed in those locations. Which means there is no need to run it by > hand. Just because this automatic usage is popular should not be the reason to block other usage which upstream IM package developer sometimes ask to use for trouble shooting the system. Osamu -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
