My laptop is toast and I only have my Slackware box ... so I don't want to screw it up before it's time to move to Slackware 14.2, which I hope isn't too much longer--

I mainly have been using Mate Desktop 1.10.2 and thought about upgrading to 1.12 for now but can't remember exactly how I actually installed it initially. It's been a long while ago and I guess I've had a bad brain dump.

I have the /dep /base /extras folders from the UK site with the msb files; but not sure if that is what I ended up installing or if it was from sbopkg ....

I've wondered too how could I roll the currently installed Mate into a single package (.txz) file.

So, basically I'd like to ask how did you install / upgrade Mate ...and which is the preferred installation method ?

It's advisable to clone the git repo and build the packages yourself but these packages are available for your convenience.

Try here at this link:
https://mateslackbuilds.github.io/

http://www.linuxquestions.org/questi...ckware-938148/

HTH

Do you prefer to install software with slackpkg or by using pkgtools?

There is a lot of information on the project page: https://mateslackbuilds.github.io/

I just pointed my slackpkgplus.conf to the url for the specific version I wanted to use.

Here is the MATE 1.12 for slackware 14.1.

http://slackware.uk/msb/14.1/1.12/

Or if you choose to build from source, here is the x86_64 read me,

http://slackware.uk/msb/14.1/1.12/x86_64/MSB_README.TXT

I use both slackpkg and pkgtool ... I tend to remove with pkgtool and install with installpkg.

I've a copy of the repos as it suggested but all those files .... I think I processed /dep first, then /base but can't remember the approach I took to keep it from being too time intensive.

there are no changes in the package name from 1.10 to 1.12

1 members found this post helpful.

Thanks for the code, it worked like a charm.

Used lftp to mirror the Mate 1.14 files under testing from slackware.uk and ran above command in my local copy of the http://slackware.uk/msb/testing/1.14/x86_64/ directory.

Then I decided to remove kde/kdei/xfce package sets using the appropriate slackpkg commands...

And blacklisted kde/xfce package sets in /etc/slackpkg/blacklist using the patterns...

I then had to add my UK keyboard layout in Mate | System | Preferences | Hardware | Keyboard

Result is very familiar from the Gnome 2 years. Thanks very much for this work.

I was able to install MATE by grabbing their GitHub repo and running the included scripts. To handle updates, I use slackpkg+ and added the MATE repo to it. Went off with out a hitch.

I have been running MATE 1.14 on -current for about 1.5 weeks. My only complaint is that the Enigmail add on for Thunderbird fails to encrypt my out going mail while the gnome-keyring-daemon is running.

I was working around this by not upgrading enigmail to 1.9.1, but I feared the lack of security fixes. So now I kill the gnome-keyring-daemon every time I log into a new MATE session, and everything works as expected.

the solution is to downgrade enigmail to 1.8.2 from here until 1.9.x received proper fix.

So far, there's no mentioning about security vulnerabilities, just removing support for GnuPG 1.x and requires GnuPG 2.x for enigmail 1.9.x

Good to know. I was concerned only about the fact that I had to keep automatic updates of enigmail off. Otherwise every time I open up a new session of Thunderbird enigmail gets updated to 1.9.

I'm using the MATE 1.14 testing binary packages from slackware.uk/msb on a current 64 bit install, so testing to the power 2.

Atril was not able to load pdfs this morning after upgrading and I noticed changes in the poppler libraries so I *guessed* that I would need to recompile Atril against the new poppler.

I was able to grab the slackbuild for just Atril from

https://github.com/mateslackbuilds/msb/tree/1.14/extra

and recompile just that package against the new poppler fine.

A quick removepkg then installpkg restored the functionality.

Just in case it helps. I'd appreciate confirmation or clarification on my guesswork

Yes, that's normal since atril will link to poppler and since last update bump the soname library, everything that are linked to poppler should be rebuilt.

The packages in testing will not be updated on every current update. I will rebuild everything from scratch when 14.2 gets finalized

1 members found this post helpful.

Sounds perfectly reasonable. Really nice to use, so thanks for providing the slackbuilds & binaries.