Feature added by: Felix Miata (mrmazda) Feature #313571, revision 1 Title: SuSEconfig fonts should not cycle uselessly over CJK openSUSE Distribution: Unconfirmed Priority Requester: Desirable Requested by: Felix Miata (mrmazda) Partner organization: openSUSE.org Description: By default, every time any package that is fonts or fonts-related is installed or updated, SuSEconfig fonts runs, and each such time, even when neither Java nor any configuration to indicate any fonts but western might ever be relevant, the following is spit onto the screen zypper is running on, and into its log: # ... xorg-x11-fonts-core-7.6-18.2.noarch.rpm installed ok # Additional rpm output: # warning: /usr/share/fonts/encodings/encodings.dir saved as /usr/share/fonts/encodings/encodings.dir.rpmsave # Starting SuSEconfig, the SuSE Configuration Tool... # Running module fonts only # Reading /etc/sysconfig and updating the system... # Executing /sbin/conf.d/SuSEconfig.fonts... # Creating fonts.{scale,dir} files ......... # /etc/fonts/suse-font-dirs.conf unchanged # /etc/fonts/suse-hinting.conf unchanged # /etc/fonts/suse-bitmaps.conf unchanged # Creating cache files for fontconfig ............................. # generating java font setup # Warning: cannot find a sans serif Japanese font. Japanese in Java might not work. # Warning: cannot find a monospaced Japanese font. Japanese in Java might not work. # Warning: cannot find a serif Japanese font. Japanese in Java might not work. # Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work. # Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work. # Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work. # Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Java might not work. # Warning: cannot find a sans serif Korean font. Korean in Java might not work. # Warning: cannot find a serif Korean font. Korean in Java might not work. # Finished. # Starting SuSEconfig, the SuSE Configuration Tool... # Running module fonts only # Reading /etc/sysconfig and updating the system... # Executing /sbin/conf.d/SuSEconfig.fonts... # Creating fonts.{scale,dir} files ......... # /etc/fonts/suse-font-dirs.conf unchanged # /etc/fonts/suse-hinting.conf unchanged # /etc/fonts/suse-bitmaps.conf unchanged # Creating cache files for fontconfig ............................. # generating java font setup # Warning: cannot find a sans serif Japanese font. Japanese in Java might not work. # Warning: cannot find a monospaced Japanese font. Japanese in Java might not work. # Warning: cannot find a serif Japanese font. Japanese in Java might not work. # Warning: cannot find a sans serif simplified Chinese font. Simplified Chinese in Java might not work. # Warning: cannot find a serif simplified Chinese font. Simplified Chinese in Java might not work. # Warning: cannot find a sans serif traditional Chinese font. Traditional Chinese in Java might not work. # Warning: cannot find a serif traditional Chinese font. Traditional Chinese in Java might not work. # Warning: cannot find a sans serif Korean font. Korean in Java might not work. # Warning: cannot find a serif Korean font. Korean in Java might not work. # Finished. If Java is not installed, all that info is a useless waste of cycles and disk space, so SuSEconfig should skip not only the log info, but should skip even looking for CJK fonts, thus making it easier to find useful info in the log, and leaving useful info on the terminal longer. Even if Java is installed, CJK search should be skipped anyway if nowhere on the system is any indication that CJK fonts might ever be useful, such as those with only Latin fonts installed and RC_LANG in /etc/sysconfig/language is set to something neither C nor J nor K. If Java needs CJK fonts to function even on western only systems, then it should be up to it to decide if whatever it requires WRT fonts needs an update and trigger it one such time, not for each time any fonts or fonts-related package is installed or updated in an up or dup run of zypper. If SuSEconfig and Java can't be made smart enough to do as described above, then at the least a new option(s) in /etc/sysconfig/suseconfig should permit choosing when and/or how often it runs its fonts module instead of having to disable SuSEconfig entirely. Or, /etc/sysconfig/fonts-config on western systems could be defaulted to no for: GENERATE_JAVA_FONT_SETUP, and/or GENERATE_OOO_FONT_SETUP. -- openSUSE Feature: https://features.opensuse.org/313571