https://release-monitoring.org/
However, they ... lack information about which versions suffer from
some CVEs. I realize that adding such information is a non trivial
task, but such information would be really useful. In most cases you
do not want to update just because there is a newer version, you want
to update because your current version has a more or less serious
problem or because the new version has a feature that you want.
the locally installed version was (and in at least some cases still is)
so far out of date that upgrading is likely to introduce significant incompatibilities (resulting in needing to rewrite local configurations nearly from scratch). I would have preferred to have addressed such
cases incrementally, rather than look at a major update.
I think it's much easier to investigate a small handful of software
titles that you know have updates, and review their changelogs to
determine whether you want to go ahead, than it is to manually try to
track dozens or even hundreds of software upstream sites looking for any
that might need attention.
The majority (*vast* majority) of third-party software that I install
locally is user-mode ... and user-space ... The days of needing to
install openssh locally, or a web server, etc. are long gone.
A CVE about a buffer overflow in a bit of software that reads (... for example ...) the exif data out of the raw file from my digital camera
isn't really something that I'm going to get very concerned about.
there are 145 unique locally built and installed software packages.
I shudder at the thought of trying to tally up the total number we had
at work.
So, ok. I'm curious enough to ask you my original question: what do you
do to track version updates of locally built and installed software on
your systems (either at work or at home; ideally, though not
necessarily, staying within the context of Slackware Linux)?
... In my case, I bite that bullet whenever I upgrade to a new
version of Slackware.
... as long as you stay on a stable version of Slackware, official
Slackware package updates usually do not break things.
Whenever I jump on to a new version of Slackware I spend about 100
hours to configure it as I want and add third party software. For
that reason, during the years, I have not jumped on to every new
version of Slackware.
However, about once every third year it might be a good idea to update
and lately there have been many years between the stable versions.
Maybe you also prefer to run Slackware current rather than a stable
version of Slackware?
It makes sense for a bleeding edge distribution like Fedora to
maintain such a database keeping track of the latest version of
every software.
... I really like the convenience of the stock Slackware packages
getting official security updates.
The third party multilib and compat32 packages do also get updates
on some kind of "best effort basis", ...
... Packages from slackbuilds.org differ very much in freshness
depending on their maintainers.
Yes, at work there are more software packages and to those software
packages I also add my custom configuration packages. ...
The tool that I use both to check if my third party packages are up-to-
date and to install third party packages is slpkg.
However, I take most of my third party packages from
slackbuilds.org. Also, I usually do not upgrade my third party
packages just because there is a new version.
... if someone wants some new version of a tool or a library like
cuda I keep the old version installed on the system disk and add
the new version to an NFS disk where users get access to newer
versions with a tool which much resembles Environment Modules: https://modules.readthedocs.io/en/latest/ Such a solution allows
different users to use different versions of the same software for
different purposes.
The nice thing with your tool is that it will show the latest
version from upstream while slpkg only shows the latest version
supported by the SlackBuild script maintainer.
However, slpkg is only used to check for updates and initial build
of Slackware packages. All my Slackware systems mount an NFS share
containing the slackware64 directory for their Slackware version.
... It also contains a directory "cus" with my custom packages and
"opt" which contains packages I only install on some machines ...
... And most of all it contains a directory called "updates" which
contains symbolic links to updated packages in the patches directory
or in my "cus" directory.
In that directory, there is also a copy of /etc/slackware-version
and a Makefile which makes sure that all linked packages have or get
their corresponding entry below /var/ log/packages after checking
that it is run on the right version of Slackware (I once made the
mistake to manually run make in the wrong directory). This Makefile
is called from a cron job in /etc/cron.hourly.
There aren't going to be any official security updates for those from Slackware. You need to look for them yourself.
Many of them might even be far out of date (at least of those that I've checked on; I mostly use SlackBuild.org more as a reference, rather
than a source for build scripts; "how did this package get handled by
that maintainer").
in my case, if a user needed a particular (usually newer than we
already had installed) version of some software, we'd find out about
its existence through them. It would have been nice in at least a few instances to just have it already available.
On 2026-05-28, Henrik Carlqvist wrote:
The tool that I use both to check if my third party packages are up-to-
date and to install third party packages is slpkg.
I'm not familiar with that. Mostly, though, (perhaps with a small
number of exceptions), I don't install pre-built third-party packages. I build locally into a Slackware-compatible package, and install that.
It *is* however, intended to help me keep up with *knowing* that a new version is available so that I can decide to update it if it
seems appropriate to do so.
However, your comment suggests to me that the SlackBuild script
maintainers themselves *could* use my script just to monitor the
packages for which they maintain SlackBuild scripts.
It would reduce the amount of work involved in just knowing that new
versions are available.
... It also contains a directory "cus" with my custom packages and
"opt" which contains packages I only install on some machines ...
... *that* I haven't done on my local mirror, but I have pondered
something very similar.
... And most of all it contains a directory called "updates" which
contains symbolic links to updated packages in the patches directory or
in my "cus" directory.
ohhh... that's too much manual maintenance, at least in how I'm
imagining your updates directory is populated.
... I wish there were some mechanism like the official stable
Slackware ChangeLog.txt that says there is now a security update
for package X, but you can feel safe because upgrading is not going
to break anything for you. ...
For simple tools, yes, in most cases you can simply change the
version number in the SlackBuild script and it will work for the
newer version.
... the big advantage of slpkg is that it automagically handles
all those nested dependencies described by the .info files at slackbuilds.org.
It *is* however, intended to help me keep up with *knowing* that
a new version is available so that I can decide to update it if
it seems appropriate to do so.
Nice with easy access to knowledge helping you to make informed
decisions.
I also make my own custom installation media which installs all
the packages in "cus" after the official Slackware packages has
been installed. Those custom packages are not only extra software,
but also some configuration files intended to overwrite the stock
Slackware configuration files.
I apologize for turning your thread about your nice tool to a
discussion about Slackware administration.
I've long considered something like that for my own installations, but
have settled instead on using cfengine for that purpose. I'm still in
the process of turning my local configurations into a cfengine policy.
No apology necessary. This sort of discussion is exactly what has made
this newsgroup worthwhile, and it's nice to see that it can still
happen.
The advantage of cfengine is that it is not limited to Slackware. If
I were managing some mixed environment with also other Linux
distributions or even *BSD or old Unix systems cfengine would
probably be a better choice also for me.
The advantage of my system with Slackware packages containing all
the configurations is that I next to the a, ap... patches, "cus",
"opt" and "updates" have yet another directory called "unnet".
I'm sure you'll relate to the notion: When you apply OS distribution
supplied software updates, and they also update their configuration
files, you don't need to remember to reapply any local changes
I realize that I may be sounding like I'm trying to convince you to
switch to cfengine; I'm not;
Yes, exactly! And I wish there were some mechanism like the official
stable Slackware ChangeLog.txt that says there is now a security update
for package X,
but you can feel safe because upgrading is not going to
break anything for you.
I just found a rather nice web-page /database at https://repology.org
which shows packages latest versions, legacy versions and outdated
versions. It also shows which versions do have known CVEs.
However, it was a really nice database and web pages which also lists statistics about Stable Slackware 15.0, Slackware current and
SlackBuilds.
Hrmmm... They appear to be tracking ... for lack of better terminology
... pre-packaged packages.
Although they do include SlackBuilds, they're assuming that the reader
is not deviating from the versions profiled on SlackBuilds entries.
... and unless it's there and I'm just
not seeing it, they're not providing a means by which their data can
easily be queried programmatically for latest stable versions.
Perhaps, but speaking for stable Slackware and Slackware-current,
necessary updates are made available rather promptly and announed on a mailing list and in a changelog that's easy to find. I don't need to
track these myself, I just need to compare today's changelog with
yesterday's to know what is newly available.
As for SlackBuilds, since there isn't regular tracking done for updated versions of each bit of software profiled on their site, that's the sort
of thing that my script can be helpful for, without the sysadmin needing
to periodically go out and check for each installed package. Configure
the list of locally built packages, set it to run from cron at a
suitable interval, and carry on with other tasks.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:59:57 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,585 |