A few weeks ago, Valve‘s official Linux binaries for its steamclient got an update. The 220.127.116.11 version is built using an updated Steam client:
Client timestamp 1676336721 (2023-02-14)
Steam Runtime version 0.20221019.0
The steamclient package which I create from this release tarball is meant to bootstrap the installation of Valve’s Steam gaming platform on your Slackware computer. The package installs a couple of scripts and a 32-bit Linux runtime based on Ubuntu, and adds a desktop menu entry so that you can easily start Steam.
When you first start ‘steam’ from the menu or from the X terminal command-line, the client scripts will download a larger set of runtime libraries, including 64-bit support. From then on, the steamclient will keep its runtime libraries up-to-date automatically, every time it starts up and connects to the Steam servers.
The Slackware package has a couple of tweaks because we obviously do not have all the expected Ubuntu tools on board. With the help of these tweaks, Steam works out of the box on Slackware – both 32bit and 64-bit with multilib!
If you are using Steam for gaming, be sure to check out its Slackware community. It’s not really chatty in there but last time I checked, the group listed over 400 Slackware users and there’s always a few online and playing.
The Wine developers released version 8.4 last week. There’s lots of bugfixes of course, but the announcement also mentions that the work has started on a Wayland graphics driver. Note that in the previous 8.3 release for which I did not create packages, Smart Card support was added, using PCSC-Lite for which I also have a package.
I have created and uploaded fresh Slackware packages (targeting 15.0 and -current) for pure 32bit Wine as well as a 64bit Wine which also contains the 32bit WoW64 (Wine on Wine64) binaries. Both packages have the ‘staging‘ patches applied and contain Gecko (the Wine implementation of Internet Explorer) and Mono (the open-source and cross-platform implementation of the .NET Framework).
The external dependencies for this package remain the same: FAudio and vkd3d are required.
On 64bit Slackware you need to have multilib installed (read the docs). In addition to a standard multilib package set, in addition you need to convert the 32bit versions of the FAudio and vkd3d packages to ‘compat32’ packages and install those.
Note: the MinGW-w64 compiler suite is used to generate the native Windows DLLs in my wine package. This compiler is not needed when you just want to run wine. If you want to compile your own wine, you can install MinGW-w64 from my repository.
You’ll have noticed – as indicated earlier, the Chromium packages for Slackware 14.2 are no longer being updated.
Today I made available the Slackware packages available for Chromium 111.0.5563.64, and they are accompanied by the un-googled version. This latest release squashes a massive 40 vulnerabilities, none labeled critical, but it’s wise to keep your systems uptodate nevertheless.
These new packages are targeting Slackware 15.0 and newer.
I skipped LibreOffice 7.5.0 because I was too busy at the time, but last week there was a release of LibreOffice 7.5.1. I got stuck in my attempts to change my chromium SlackBuild script to run more efficiently on Slackware 15.0, so it seemed like a good time to work on something else than a Google product.
But as with many software products that make a version jump, updating the Libreoffice build script was not completely trivial. Not as bad though as with Chromium. Eventually, I was able to come up with nice working binaries and I have already uploaded those to my repository and its US and UK mirrors.
These packages are targeting Slackware 15.0 and newer.
Note that my libreoffice package depends on openjdk11.
The link above to the release announcement also lists the most important new features that come with LibreOffice 7.5.x. Well worth checking out.
I have uploaded the packages for Google Chromium 110.0.5481.77 as well as its un-googled version. The sources for this new major release were available since a week ago, but as it often happens when Chromium updates its major version number, I get to find ways around the breakage that seems to be specific for the unusual Slackware target, and create fixes and patches to make the sources compile into a package for Slackware.
The new packages are targeting Slackware 14.2 and newer. As announced last year and repeated a couple of times, I am going to drop support for Slackware 14.2 on the first anniversary of Slackware 15.0, which is February 22nd, 2023.
Ergo, the final version of Chromium you’ll get from me for Slackware 14.2 will be this “110” release because Chromium 111 will see the light on March 1st.
It would be wise to upgrade to Slackware 15.0 anyway if you are still on 14.2.
Dear visitor, you seem to be using an Ad Blocker. Please consider whitelisting 'Alien Pastures'. I use the revenue from displaying ads (small as it is) to keep this site running. Thanks!