On wto, Jun 4, 2019 at 8:59 PM, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
All,
I'm working the loss of icons in yast2-control-center-qt3 from 15.0 -> 15.1 (http://bugzilla.suse.com/show_bug.cgi?id=1136295). I have been successful in restoring most icons using the png icons and symlinks, e.g.:
yast-hardware-group.png -> yast-hardware.png yast-misc-group.png -> yast-sysconfig.png yast-network-group.png -> yast-network.png yast-security-group.png -> yast-security.png yast-software-group.png -> yast-software.png yast-support-group.png -> yast-support.png yast-system-group.png -> yast-system.png yast-update-online-configuration.png -> yast-online_update.png yast-update-online.png -> yast-online_update.png
The links are needed as there was somewhat of a random renaming of icon basenames between 15.0 and 15.1. Some Yast package uses the basename of the icon in searching for the appropriate icon to use. Does anyone know what package holds this mapping so I can see what additional mappings were renamed?
The renaming was hardly random, and it was a cleanup after years of negligence of yast-theme. No package in particular holds that mapping, the closer you will get is breeze5-icons, which has majority of YaST icons supported upstream. Icons for modules are loaded based on desktop file in each module, and each module provides its own icon (at least they should do that). Otherwise the best bet is to go through 70 repos that provide desktop files and icons and get that info from there. I just did that a few days ago when updating YaST desktop files to reverse dns schema [1], with swap for Name -> GenericName and GenericName -> Comment for the sake of having a different name for modules on the desktop than in ycc (Now modules mention that they are from YaST, which makes searching through them in desktop environments with other applications that might have shared the same name before a little bit easier). Now I need to figure out translations there properly, and probably a million other fixes to make YaST work better with everything else in the systems. Also from my pov, ycc-qt3 is not sustainable, but I break YaST every week, so I might not be the best arbitrator. [1] https://github.com/yast/yast-yast2/issues/934 LCP [Stasiek] https://lcp.world -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org