that need it; in the future more and more ports will move to meson build anyway.
I first though I'd set CONFIGURE_STYLE in gnome.port.mk but it's too fragile
(MODULES list must be sorted very carefully).
Less magic is good.
discussed with jasper@
instead. It is just too hard to maintain a coherent list of still
reachable homepages for GNOME projects so use wiki.gnome.org which is
the entry point for *all* GNOME apps.
unconditionally. Instead, don't check for the existence of index.theme.
This will allow us to catch errors that may be happening because of a
missing dependency in the chain.
Some hidden issues may appear, in which case please contact me.
discussed with and ok blind jasper@
The reason is that if a theme is removed after updating to a new version,
then we are left over with a useless cache file because we are using
pkg_add -u and not pkg_delete.
Rational: except for QT/KDE ports, gtk+2 should already be in the
dependency chain for ports installing share/icons/ files (i.e. no need
to explicitely add it) and if we have svg icons without their png
counterpart and librsvg is not part of the dependency chain then we
explicitely add it.
gnome-icon-theme is the inherited theme for most icon themes so we
make sure we have gtk-update-icon-cache and can display svg icons.
landry@ agrees
PLIST and delete everything under the @sample'd directory instead of the
directory itself to prevent a warning from pkg_delete(1) trying to
remove a non existing directory and to help preventing left-over files
and directories.
Work around this by installing, alongside gnome-icon-theme, a system-wide
gtkrc containing the line:
gtk-icon-theme-name="gnome"
This avoids assertion failures regarding missing icons with GTK+
applications when executed outside of a Desktop Environment like GNOME
or XFCE.
Also remove x11/gtk+2/pkg/MESSAGE-main which is no longer needed.
Problem noticed by Patrick Keshishian
Discussed with and OK ajacoutot@
