First off - thanks for your efforts with this Chess.
I did a git clone, ran base/mate-build-base.sh and it fell over when it got to gtk-engines with "
You must have automake 1.7.x installed to compile".
So I replaced ./autogen.sh in the SlackBuild with ./configure and it got through the configure process and built. I realise this is probably not as robust but I'm curious to see what Mate looks like.
I am building on slackware64-current (March 20) BTW.
The rest of base and extra was uneventful. I pushed my luck and went into testing as well, and I have a few comments:
(1) mate-screensaver - the SlackBuild needed the old -L/usr/lib64 trick in
elif [ "$ARCH" = "x86_64" ]; then
SLKCFLAGS="-O2 -fPIC -L/usr/lib64"
(2) mate-system-monitor required me to first install libgtop.
(3) mate-text-editor required me to first install gtksourceview.
Just logged out of KDE and logged into Mate desktop without rebooting and everything seems to be working.
I spoke too soon. When I launch mate-terminal I get this:
(mate-terminal:3356): GLib-GIO-ERROR **: Settings schema 'org.gnome.system.proxy.http' does not contain a key named 'use-http-proxy'
I am explicitly using a proxy (Squid). If I go into "Control Center" and then "Network Proxy" and change to "Direct internet connection", mate-terminal launches fine. Perhaps this is an upstream problem though, because there is no matching key in that schema:
fskmh@workstation:~> gsettings list-keys org.gnome.system.proxy.http
Tried the following and I can confirm that it does not work:
fskmh@workstation:~> gconftool-2 --set /system/http_proxy/use_http_proxy --type bool true
fskmh@workstation:~> gsettings set org.gnome.system.proxy.http host '127.0.0.1'
fskmh@workstation:~> gsettings set org.gnome.system.proxy.http port 3128
fskmh@workstation:~> gsettings set org.gnome.system.proxy mode 'manual'
I suspect that something has to be recompiled with this key enabled.