I second this, would be nice to have P7zip already included, and even configured with desktop context, because I am lazy and too dumb (mostly the latter :p) to get P7zip to work correctly and have context menus on my WMs.

network-manager-applet-1.8.12:

http://ftp.gnome.org/pub/gnome/sourc...et-1.8.12.news
http://ftp.gnome.org/pub/gnome/sourc...-1.8.12.tar.xz

emacs-26.1:

http://www.gnu.org/software/emacs/index.html#Releases
ftp://ftp.gnu.org/gnu/emacs/emacs-26.1.tar.xz

I just built emacs 26.1 here. Seems ok. I don't know about anyone else but I prefer it built against the lucid toolkit: it avoids some gtk warning messages and a longstanding bug with the emacs server when built against gtk.


BTW, there are some new configure options.

--with-gameuser=":games" is now required to keep using the current shared games scores files in /var/games/emacs. Without it games scores are per user and stored under ~/.emacs/games. If you choose not to add this option then you might as well remove /var/games/emacs/ entirely.

--disable-libsystemd without this the emacsclient/emacs --daemon server process connection tries to use systemd socket activation, it still appears to work, but throws out warnings. update: actually it looks like it still throws out the warnings even with this option, so perhaps it's just something that happens now when you run emacsclient -a "" and have the daemon process implicitly started. Apologies for the noise on this one.


--disable-build-details This is a new config option, it's not essential, but I added it here as I don't have any use for build details.

Other than those, my personal preference is for:
--with-x-toolkit=lucid
--without-toolkit-scroll-bars
... but that's just me. :)

I have noticed that a few graphics aren't showing in its webbrowser mode though. I need to investigate whether that's down to my choices of toolkit and whether it was happening with 25.3. I'll report back. update: ok, the missing image is also happening with the stock 25.3 package from current, so that's not new to 26.1. update2: Mystery solved. The idiotic GNU webpage designer created a black image with transparent background... which is fine unless you're using a theme that has a black background. LOL. Nothing to see here, move along! ;)

Can't be done with amdgpu-pro. It repackages a lot of extras like proprietary builds of a lot of xorg packages, llvm, mesa rebuilds, libdrm... it's just a bloody f---ing mess. If you need the extra functionality, just grab libtxc_dxtn and driconf from SlackBuilds. Much less a headache to deal with.

fftw-3.3.8:

http://www.fftw.org/release-notes.html
ftp://ftp.fftw.org/pub/fftw/fftw-3.3.8.tar.gz

stunnel-5.46:

https://www.stunnel.org/sdf_ChangeLog.html
https://www.stunnel.org/downloads/stunnel-5.46.tar.gz

Just a heads up that with the mesa git master you no longer will need libtxc_dxtn. This might also apply to the mesa version in current?

Did the embargo on s3tc and dxtc get lifted finally Orbea?

Yes.

https://phoronix.com/scan.php?page=n...ires-Next-Week

That was an itch I had to scratch. Adrien's repository was something I ran into by accident some years ago, perhaps it was ponce even then who told me. It looks like Adrien simply commits the whole of ./source directory to his git repository, using a .gitignore file to avoid the source tarballs getting committed as well.

But I thought that's too simple, and wrote a script to create a (more generally useful IMO) repository tracking the whole slackware64-current directory tree, additionally unzipping all the compressed files like the patches, doinst.sh scripts etc.
More readability in the cgit interface and better diffing.

See https://git.slackware.nl/current/ - there's only one commit (the initial one) but I scheduled the script in cron to update the repository on every public update of the ChangeLog.txt in slackware64-current.
Hope it's useful to someone :-)

git-2.17.1:

(CVE fix)
https://raw.githubusercontent.com/gi...tes/2.17.1.txt
https://mirrors.edge.kernel.org/pub/...-2.17.1.tar.xz

rust-1.26.1:

https://blog.rust-lang.org/2018/05/29/Rust-1.26.1.html
https://static.rust-lang.org/dist/ru...6.1-src.tar.gz

ImageMagick-6.9.9.48:

https://www.imagemagick.org/download....9.9-48.tar.lz

FVWM 2.6.8
 

Forwarding an email from Thomas Adam to the main mailing list:

After upgrading some machines to the latest slackware-current (from kernel 4.9.67 to 4.14.44) I get following warning in syslog after each reboot
This disappeared after updating from mcelog-153 to mcelog-158:
https://git.kernel.org/pub/scm/utils...ce/mcelog.git/

Another new imagemagick-6.9.9-49:

https://www.imagemagick.org/download....9.9-49.tar.lz

The mesa driver, for the most part, works just as good, if not better, than amdgpu-pro with a lot less headache. But, AFAIK, the amdgpu-pro driver doesn't support Xorg 1.20, so you can't get a working amdgpu-pro driver on -current unless you downgrade Xorg. I do have SlackBuilds available for several different versions of the driver, but I don't think any will work on -current (but 17.10 and below should function on 14.2).

https://github.com/bassmadrigal/slac...gpu-pro-driver

How many times do I have to tell you this? amdgpu-pro *can* be repackaged into a Slackware package that doesn't affect the base packages (and uninstalls cleanly). I've done it with past versions, but I haven't kept it up to date for three reasons:

1. I don't have the hardware to check it.
2. There doesn't seem to be much of a demand for it (especially with the performance of the mesa driver).
3. amdgpu-pro 17.30 and newer require Xorg 1.19, which, at the time, was only available in -current (which I don't normally run), but current has now been upgraded to 1.20, so there isn't even a version that will work with -current.