FS#15591 - [namcap] hicolor-icon-theme confusion
Attached to Project:
Arch Linux
Opened by Allan McRae (Allan) - Monday, 20 July 2009, 01:50 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Wednesday, 23 February 2011, 23:15 GMT
Opened by Allan McRae (Allan) - Monday, 20 July 2009, 01:50 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Wednesday, 23 February 2011, 23:15 GMT
|
Details
Description:
Namcap is conflicted about whether we need hicolor-icon-theme for a package. When it is not added, it complains that the hicolor icon theme cache needs updated and to add a hicolor-icon-theme depend. After adding that, it say there is an unneeded dep on hicolor-icon-theme |
This task depends upon
Closed by Rémy Oudompheng (remyoudompheng)
Wednesday, 23 February 2011, 23:15 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in upcoming version 3.0
Wednesday, 23 February 2011, 23:15 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in upcoming version 3.0
Currently namcap suggests hicolor-icon-theme as a dependency
when it does not find it in the depends array and the package
has files in /usr/share/icons/hicolor. It _does_ not check
whether hicolor-icon-theme is already in the dependency chain.
Now, when you add hicolor-icon-theme to depends=(), hicoloricons
module is happy but the depends module detects the fact that
it's already in the dependency chain and complains.
This happens because the hicoloricons module does not have access
to the depends module information. Sharing information between
modules is on the TODO list for the next 2.x release.
E: The hicolor icon cache has not been updated even though there are files in /usr/share/icons/hicolor. Use gtk-update-icon-theme or xdg-icon-resource to update the icon cache.
I think you mean gtk-update-icon-cache instead of gtk-update-icon-theme.