diff options
| author | Michael Palimaka <kensington@gentoo.org> | 2016-08-06 02:06:06 +1000 |
|---|---|---|
| committer | Michael Palimaka <kensington@gentoo.org> | 2016-08-06 02:06:20 +1000 |
| commit | 1c31a12ab95fc7d66b83aae51dfed147cf633090 (patch) | |
| tree | cae608553302f9d60558ea94ef7dffbe01eaf674 /eclass/cmake-utils.eclass | |
| parent | 5a4dfd12ba10bec7ebfaaef73fcd14e31fe6d9f1 (diff) | |
| download | kde-1c31a12ab95fc7d66b83aae51dfed147cf633090.tar.gz kde-1c31a12ab95fc7d66b83aae51dfed147cf633090.tar.bz2 kde-1c31a12ab95fc7d66b83aae51dfed147cf633090.zip | |
kde-plasma/breeze-gtk: install theme for gtk-3.20
breeze-gtk includes multiple theme versions, targeting different GTK versions.
Previously the older gtk-3.0 theme was unconditionally installed despite newer
versions for gtk-3.18 and gtk-3.20 being available.
Upstream commit 93eb6e6ebcb825cd7b740069f02bc6ea3995aa19 changed this
behaviour, introducing the build option WITH_GTK3_VERSION to select the
appropriate theme version and install it to /usr/share/themes/Breeze/gtk-3.0.
This option is not particularly useful for Gentoo as we currently ship both
gtk-3.18 (stable) and gtk-3.20 (unstable) and there is no way for us to trigger
a breeze-gtk rebuild if the gtk version changes.
According to the documentation[1], GTK will search
/usr/share/themes/<theme>/gtk-<version> and then earlier versions all the way
back to 3.0. We therefore manually install the gtk-3.20 theme version to its
versioned directory alonside with the older theme in its default location to
ensure that the theme works correctly regardless of GTK version changes.
In the future when <gtk-3.20 is removed from the tree we can remove this
workaround and build with -DWITH_GTK3_VERSION=3.20 instead.
1: https://developer.gnome.org/gtk3/stable/GtkCssProvider.html#GtkCssProvider.description
Package-Manager: portage-2.3.0
Diffstat (limited to 'eclass/cmake-utils.eclass')
0 files changed, 0 insertions, 0 deletions