[Slackbuilds-users] Updates - 20260822.1

[B. Watson]

On Sat, 22 Aug 2026, Willy Sudiarto Raharjo wrote:

> Maintainers, please make sure you test all the scripts you submitted on
> Slackware 15.0 machines, either in bare metals or inside a VM or chroot
> environment to make sure it works for Slackware 15.0.

Addendum: by "15.0", we mean:

1. 15.0 (NOT -current)

2. with all patches applied from patches/ (e.g. via "slackpkg upgrade-all")

3. *WITHOUT* anything from testing/

In particular, this means you CAN'T use the new glibc, binutils,
gcc[*], etc from testing, when you're testing your scripts for 15.0
compliance.

If you're not already using sbo-maintainer-tools to check your builds
and built packages, I strongly recommend that you start using it. In
particular, sbopkglint now (as of last week) checks for bad glibc
requirements and emits an error. We run sbolint and sbopkglint on
all submissions (including ones made via PR/MR), and anything that
fails the checks will be rejected.

It's possible to convince us that your build should be accepted
(e.g. that the checks are too strict), but that will be considered
on a case-by-case basis, and will require human interaction (you,
the maintainer, are going to have to explain and justify it to the
admins). It's not as scary as it sounds, we don't bite...

[*] If you really do need a newer gcc, you can use REQUIRES="gcc14"
(since we have that in our repo already). Don't do this lightly
though: please try to find a way to patch the code to compile on
15.0's stock gcc (11.2.0) or clang (13.0.0), and only resort to gcc14
if it's *really* required. It should be the last resort, not the first
thing you try.