[Slackbuilds-users] cmake3.30.SlackBuild category and naming

[B. Watson]

On Sat, 19 Oct 2024, Andrzej Telszewski wrote:

> You use it the exactly the same way you do now.
> Just in REQUIRES it would become "cmake-opt".

When I did this for Slackware 14.2, I called mine "cmake-202x". That
was out of irritation (it was 2022 or so, and we were stuck with a
cmake from the previous decade)... cmake-opt is a better name, though.

> My general idea for these *-opt packages is that, that we keep them in 
> repo forever,
> even if next Slackware ships the required versions.

I don't think that's going to happen. There no sense in spending
time/effort maintaining a whatever-opt package if Slackware has a
'whatever' that's the same version or newer.

This is a long-standing policy for SBo, goes back to the beginning.

> The point is that, at some point, we will need them again, so they can 
> be easily re-used.

Yes. We'd remove them from the live repo, but they'd still be
available in the git history.

> We could maintain these packages at the latest stable versions from 
> upstream.

If the latest stable upstream version is *newer* than what's in
Slackware, that makes good sense. But not if it's the same version.
That's just extra effort for no gain.