The pkgtools work like this by design. No need to fix anything.

I use sbopkg ncurses (I think) manager similar in looks to pkgtool. I've never had downgrades with it. It will tell me if I have a newer package. Occasionally I'll install a newer package than what is available at Slackbuilds. It has a queue where you adjust order and decide if packages will be upgraded or not. If a mistake happens it is user error. https://sbopkg.org/

It also lets you edit build scripts. It saves a local copy for later use. You can delete it the local copy too. It provides all the information available from Slackbuilds. I also have created a few directories with sources and Slackbuilds with some custom edits.

everything works by design unless it doesn't, if something is designed not to do something it will not, and visa versa.

What are you talking about? It is well known that upgradepkg doesn't do anything more than to verify the package versions are different (or at least the build number at the end). You can use it to upgrade or downgrade packages.

As 55020 mentioned, freetype was recently "downgraded" in -current from 2.8.1 to 2.8. upgradepkg will "upgrade" the 2.8.1 package with the 2.8 package without any hesitation. It is how it was designed.

It is working exactly as it is supposed to.

missing leading function name

You're upgrading the package installed on the computer with the one you want to install. It could be a newer or older version.

If it were to manage version numbers and only install them if they're newer, how is it supposed to differentiate between to commit IDs on which on is newer? cf142a4 could be a newer or older version of 4fd95a2. Or to know if 2.7.9 is newer or older than 2.7.10? Or when they throw letters in it like OpenSSL. Could you imagine trying to build the regex to figure all that out?

Rather than adding all the complexity to the program, upgradepkg is used to upgrade the package that is installed with the one you want to install, no matter what the versions are.

1 members found this post helpful.

it all started with sbotools when someone posted the docs to it, showing within the docs the upgrade all so I did it just to see what I'd see and it said blender upgrade y ? so I said why not maybe that one finally updated it page on slackbilds so I said y and I noticed it put me back a version, and well I posted it, and here we are ....

It works the same as Slackware's upgradepkg, so there's nothing wrong with it. Just because you expect something different doesn't mean the program isn't working as it was designed to.

the scapegoat phrase, it is designed to work that way .. I was merrily pointing out that to the one that is trying to upgrade something that it doesn't necessary upgrade because it downgrades too ...

so obviously the name upgradepkg is misleading

As I said earlier...

it is not upgrading when you downgrade .. you can say that all day long to me and It is still not upgrading when you're.

yeah I upgraded to a 1809 used car from my 2017 one. .. its ok it is designed to not turn corners like my other one.the door falls off too but that is ok it is not designed to last that long.

I am not that gullible

Get over it.

2 members found this post helpful.

It is not the form of upgrading that you're used to, but Merriam-Webster defines an upgrade as an improvement. If the newer package is broken, then the improvement/upgrade would be to use a lower version.

There's multiple meanings to a word.

2 members found this post helpful.

you and the others are the ones trying to push a lie onto me and keep posting to me on this, I'm just replying, and calling a function with the word upgrade in it when it is installing everything no matter what version it is regardless of what version is already install, it not upgrading when it is a lesser version being replaced.

period.

saying it is designed to do what it does, really?

I can write a function and call it update_everything() then have it delete whatever I want while updating something else, and tell people their is nothing wrong with it, it is designed like that , no need to fit it, same thing.

upgradepkg is misleading because it can downgrade as well, I post a true and you're defending a lie. upgrade is upgrade and downgrade is downgrade. designed to do something is something anyone can do and have it NOT do what the name clearly suggest it does then take your stance on it. but why should I be that?

get over it? what do I have to get over? I am not the one trying to make you believe upgrading is the same as downgrading.

You're not wrong that an upgrade can be a version that has a higher number than the older one. But, as I posted above, there's more than one meaning to the word. You're understanding of the word upgrade is limited. You specifically state a lower version number is a lesser version? What if the new one broke something? If you're replacing something that is broken with something that isn't, is the broken one the "greater" version and the working one is the "lesser" version? How many people refused newer versions of Windows because they were lesser quality than the version they're currently using? (A lot.) You just need to understand that it is using a different meaning of the word than you are expecting.

I don't see this as any different from the people who think a fully patched 14.2 install is "current". While it is correct in one form, it is incorrect in the sense that Slacwkare's development branch is -current.

Is there a better word that could be used for upgradepkg? Probably. Is using upgrade in upgradepkg incorrect? No. Is it worth it to try and replace upgradepkg with something else? Probably not. There's far too many things out there that rely on it and most people quickly learn that "upgrade" can mean more than just a newer version. But who knows, maybe you could request Pat to change it in future releases (although, I don't suspect this would happen).