Only inherit themes which are really needed about papirus-icon-theme HOT 3 OPEN

from papirus-icon-theme.

@alexxons hi, can you please clarify in what way does the v0.18 spec change the way inherited themes work? wouldn't removing them cause missing icons for example in KDE apps, considering that not all Breeze icons are covered by Papirus?

from papirus-icon-theme.

Here the concrete line which was added to the spec.

Wouldn't removing them cause missing icons for example in KDE apps, considering that not all Breeze icons are covered by Papirus?

In theory, if Papirus provides all icons given in the icon-naming-spec, that should be sufficient. Since, if an App requires additional icons, according to the spec,that App should install these additional icons itself into the "hicolor" folder.

It might be that there are (KDE) Apps which miss installing these additional icons and rely on having breeze in the Inherit tree. If you notice so, you should report that to the app developer. If these icons are used by multiple applications, it might make sense to request a new icon-name for them on freedesktop.org, so that all themes will ship that icon.

In case you want to make sure that even such Apps which dont follow the standards are serviced with the KDE specific icons when using Papirus, it is fine to still keep breeze in the Inherits section. Though than you should make sure, that whenever Papirus is installed, as well breeze is installed (hard dependency). Since otherwise, users of the mentioned KDE Apps still won't have icons when installing only Papirus ... and they won't know why icons are missing / which theme to install to get them.

The best place to define a hard dependency to breeze probably would be, to write that into the README.md, so that packagers do know ... it might be required to open issues against distros as well, in order to inform them on the dependency.

from papirus-icon-theme.