[Slackbuilds-users] templates/ proposed updates

[B. Watson]

On Wed, 5 Aug 2026, Logan Rathbone wrote:

> The version shipped with 15.0 also supports `meson setup`, so there is
> no harm in migrating the template now.

Yeah, we get the warnings for anything using python3-meson-opt on 15.0, too.

> Attached please find a diff with proposed changes to the meson template.

Looks good. Will do some testing but I don't expect problems.

A question... does it really make sense to call ninja as "${NINJA:=ninja}"
instead of just saying "ninja"?

It exists to support samu (from the samurai build). But why does
anyone care whether a build uses regular ninja or samu? Is samu
faster?

If there are builds that don't work with regular ninja, that need
samu, we'd just write "samu" in their SlackBuilds... it doesn't look
like anyone's ever done this, though.

I mean, we have an alternate implementation of meson called "muon",
but nobody's proposed supporting it via "${MESON:=meson}" in the
template.

If someone *really* wants to use samu, wouldn't it make more sense to
have a profile.d script that sets up PATH so it has a directory with
a symlink samu => ninja, and let the user source that script? This is
how e.g. cmake-opt works.