On Fri, Feb 25, 2011 at 9:42 AM, "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote: > There is a bug about www-client/chromium icon theme dependencies > (https://bugs.gentoo.org/show_bug.cgi?id=352263), and I'm not quite sure > what's the best way to solve it. > > The main issue is that in KDE only oxygen-icons work, and in XFCE > oxygen-icons *don't* work and one needs other icon themes installed > (which in turn don't work in XFCE).
Does running KDE always mean that oxygen icons are used? If I select another icon theme in KDE system settings, I'm guessing that Chromium will switch to using that, but I haven't had a chance to test this. It is on my todo list when I get home this evening. > > Portage obviously doesn't know which DE the user is running (multiple > DE's may be installed on the system), so I don't see a way to create > "foolproof" dependencies. > > The two approaches I'm thinking about are: > > a) Drop any icon themes from RDEPEND, tell the user in pkg_postinst > about possible choices. > > b) Add "kde" to IUSE, and then kde? ( kde-base/oxygen-icons ) !kde ( all > || the || rest ) to RDEPEND. > > What do you think? Do you have some better ideas? Option (a) sounds good to me. Maybe you could add something to the FAQ section on the project page so it will show up in Google search results. Chromium should really have some generic fallback icon to use when it can't find an icon for a given mime type. A broken image icon is less than ideal for that. I guess that would be an upstream issue though.
