Lukas Ocilka wrote:
It's not a good idea to put that icon to your RPM because user can have several icon-themes installed in /usr/share/YaST2/theme/ directory at once. The current theme in use is symlinked from the "current" directory ... and yes, we know it is confusing :) ;) we now it is not ideal ...
(back to the old discussion), it actually makes sense. Otherwise a theme has to know all icons for all modules. If you look desktop environments for example, the theme provides icons: oxygen-icon-theme: /usr/share/icons/oxygen/* However, kde4-kopete also provide icons for that theme, for other themes too /usr/share/kde4/apps/kopete/icons/crystalsvg/ /usr/share/kde4/apps/kopete/icons/hicolor /usr/share/icons/oxygen/ some are specific to the application (in apps/kopete/icons), and other that are not specific, like actions that can be used by programs that depend on kopete for example (who want to use those actions). /usr/share/icons/oxygen/22x22/actions/webcamreceive.png I find this model much more consistent. It is like a solved problem we reinvent in a bad way. Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org