[Slackbuilds-users] Introducing the SlackBuild Boneyard

[B. Watson]

On Wed, 15 Jul 2026, David Chmelik wrote:

> That's good, and might be interesting someday to see the archive slowly 
> go back to the beginning.  Many were removed I wanted to see if they 
> might still work--especially games--and I still use stuff from Slackware 
> 14.n-stable extra/ on 15+current.

I limited it to 15.0 only partly to keep the archive size down, and
partly because stuff for older releases isn't generally as useful:
some of the 14.2 stuff that got removed, specifically was removed
because we couldn't get it to compile or run on 15.0 (or, because
whatever it is, was added to Slackware).

> Some of the interesting games maybe just went defunct and with
> a fork becoming more popular (even 10 or 20 years ago, sometimes
> several times over years) but I don't know. 

Yeah, I hate for games to disappear. Right now I'm updating
quakeforge, since its maintainer has been gone since 2012. It's an old
project, but there actually was a release in 2023.

Of course there are other Quake engines on SBo (darkplaces, for one).
So even if quakeforge were to vanish, we haven't lost a game...

> I have a fair number of packages I'm still interested in from old
> versions.  Some the utilities, etc., broke but never really were
> replaced with something as good or better

You could port them to 15.0. It might be a fun & interesting project.

> especially if there might be a way to automate it?

It's already automated. I just have the script only look at the git
log back to the first 15.0-* tag. I could change that to the first
14.2-* one, or have it use the whole log, but I don't think it would
be that useful (see above). Plus, the way the script works, it'd
require extra logic to figure out which Slackware version the script
was originally for (and you really would want to know that).