I do not use either package.
I am uncomfortable with automatic updates and installations. I disliked that option in Windows and I dislike the option in Slackware too. Even within individual apps, such as Firefox, I disable all such automatation.
I maintain my own local mirror of the Slackware tree. I use my own modified rsync script originally written by Eric. (Thank you Eric!). Refer to oldfolio's post for a link to the original script.
I run the rsync script daily through cron.
I receive email notifications when patches are issued.
I use a shell script that compares the patches list with what I have installed. I used the script posted by urka58 here at LQ to expand upon and create my own cross-check script:
My shell script provides me an additional message of whether the original stock package is installed. That is, if the patch is not installed but I do not have the original stock package installed, then I need not worry about installing the patched package.
I always manually install packages and patches.
The Slackware mirrors do not maintain previous versions of patched packages. I modified Eric's original rsync script such that when I synchronize and download patches, I do not delete any previous versions of patches. This allows me to revert to a previous known good package when unexpected regressions appear. I recall having to do this at least once with samba. A new samba patch was released a few weeks later.
I maintain a text file listing all non-stock Slackware packages I have compiled and installed. T3slider posted a shell script to provide this feature and is discussed at:
I run this shell script hourly through cron. My modified version of the script maintains the file in two different locations, once each on each internal hard drive in my box. I run the script hourly only because I tend to move in spurts when I compile and install new packages.
I once used kslackcheck but that program is no longer maintained. I liked that little program because I was provided a nice list of what was not installed. However, my shell scripts all do this for me now.
Writing this response took more time that what I actually devote toward maintaining patches and updates. The scripts and cron automate most of the process. Although I manually update patches, only a few are issued at any one time.