Originally Posted by beowulf999
These newer packages were created and installed via the standard slackbuild-installpkg route, for example libgpod and hplip to support newer devices.
Otherwise, top notch tool.
Is there a way to fix this?
There is not a way to fix this. (It's really not broken
)The reason being is that slackpkg only looks at the packages available in the Slackware mirror. If the currently available Slackware package is at a different version than what is installed on your PC, slackpkg will upgrade it. This is the way pkgtools in general works. Most of us think of upgrade as meaning an increase in version number. upgradepkg should be thought of and used as replace
. I particularly like this feature!!!
Slackpkg's goal and purpose is to keep Slackware pristine and inline with Slackware provided packages.
And yes, I have the same issue. As I routinely run a handful of newer packages than stock Slackware. A small PITA to uncheck the packages. Or as stated above, blacklist them. If you do blacklist them, keep up with the changelog, that way when Slackware does update the package you'll be aware of it.
If you are not already, subscribe to the mailing list. This will notify you of security updates to stable releases. RSS feeds are available for current. slackpkg also has the check-updates