gnome-themes always installs HighContrast, HighContrastLargePrint, etc. themes even with USE=-accessibility. The problem is that these themes require a corresponding engine (hcengine) from gtk-engines that is omitted with USE=-accessibility. Salient bits: From gnome-themes-2.24.3.ebuild: $(use_enable accessibility all-themes) From gnome-themes-2.24.3/configure: --enable-all-themes Install all a11y theme sets, default is core a11y themes only From gtk-engines-2.16.1.ebuild: use accessibility || G2CONF="${G2CONF} --disable-hc" I'd like to see it fixed as suggested in #100287: gnome-themes should just remove the HighContrast themes if USE=-accessibility. (I've attached a patched ebuild to do that.) Otherwise, if the sanctity of the GNOME defaults needs to remain intact, gtk-engines should always build hcengine. Reproducible: Always Steps to Reproduce: 1. env USE=-accessibility emerge gtk-engines gnome-themes. 2. Start GNOME, select High Contrast theme from Appearance Preferences. 3. Actual Results: Get an error box complaining about hcengine not being installed. Expected Results: Not display an error box.
Created attachment 194999 [details] omit HighContrast themes if USE=-accessibility
thanks for the ebuild. Please note that unified diffs against latest ebuild in tree are preferred as they are easier to review.
In 2.26.3.1 without a bump. I changed the src_install in order to gain some time, reduces the install of the package from 1 minute 5 seconds to 43 seconds here. Thanks for reporting and reminding me this bug I figured last year but forgot to fix.
