How should I update programs installed from SlackBuilds scripts?
 

The question is already asked in the title: what is the proper way of updating SlackBuilds installed programs? Should I completely remove them and install again newer version from scratch or not? I'm using Slackware for two years already, but need to update something just now.

There is a way to update through the sbopkg gui or sbopkg -c.

It's the 4th choice in the sbopkg's menu:
It says: List potential updates to installed SBo packages.;)

https://www.linuxquestions.org/quest...stions-892334/

I usually download the tar and use a slackbuild that I modify to fit that tar then run it when that is done I then run updatepkg - but you can if you want uninstall the previous one removepkg, then run installpkg too.

You don't need to remove them first and then install the new one. Just use upgradepkg.

I completely forgot about upgradepkg.

Thanks montagdude-;)

There are some possible hang ups.

Yes, sbopkg provides the update dialog which will present you with all the potential upgrades of SBo-based packages. You can select what you want and let it do its thing. However, it's possible that one program that needs to be updated could mean that one of its dependencies needs to be updated as well. It is then possible that another program that requires that dependency will now need to be rebuilt to work with the new dependency.

Some programs are super easy to upgrade while others may require rebuilding a large number of packages. When I used sbopkg, I would typically ignore most updates and only update programs when absolutely needed. When I did upgrade, I prepared myself to rebuild programs, if needed, to make sure it all worked.

What program do you want to upgrade? Knowing what it is may allow us to tell you how likely it is that upgrading it could require other packages to be rebuilt (but we might not know for sure without you trying it yourself).

But, if you use sbopkg, when you build a new package, it can install/upgrade it for you automatically. If you are building it manually, you can run upgradepkg on the new package and it will upgrade the old one. If you're using other tools, you'd need to look into what they offer.

i put updatepkg when it should have been upgradepkg sorry, sometimes I think my fingers have a brain of their own.

You also have sboupgrade from sbotools to help you out here:

https://pink-mist.github.io/sbotools...upgrade.1.html

Sbotools îs perfect for that type of routine job:
http://lilianfornea.tk/unixtuts/linu....slackware.txt

not really:
look at versions ,
I had 2.79 installed, and it back stroked on me and upgraded ( down graded ) to version 2.78c

even though I still use sbotools, now I have to redo it using my own slackbuild to put back that actual upgrade, again.
this is how it is suppose to be,

None of the Slackware package management tools attempt to parse the version strings and determine if the package to be installed is actually newer than the one they are replacing, nor should they, because there are an infinite number of possible versioning schemes. An "upgrade" is when the repository you are drawing from has a different (but not necessarily higher) version than the one you have installed. It's up to you to choose whether you actually want to upgrade the package.

By the way, this is one of the reasons why I put a blacklist function in sboui.

+1
Nothing wrong with sbotools. If you have a local package that you want to protect, blacklist it.

And meditate upon what just happened with freetype in -current

upgrade from 3.0 to 1.0 is not an upgrade it is a down grade. I don't even think Slack allows that if I remember correctly from trying to do that before, awhile back, and I don't really feel like trying to think of what I can use to prove my point, maybe later I will.

hold on let me mess with blender -- brb
wow it did screw it up
I'd think one would put a check for the version 'sizes' to be sure 2.78c is not larger then 2.79(x)
looks like a simple simple check to because the tars all have a same pattern

ugradepkg doesn't try at all to guess which version is the more recent, so it could as well be named replacepkg. Quoting the email "sent" by Patrick Volkerding to root during Slackware's installation:We just had an example...

Incidentally slapt-get (automated upgrade tool) behaves exactly as upgradepkg on that respect :D

I guess ... it is left up to operator error handling .. np

or

Pat needs to slap-get his butt up in a chair and behind the keyboard and fix that.

just kidding Pat. :D

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.

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.

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.

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).

you ever stop to think maybe Pat is misusing words where everyone else calls what "slack' calls current, they call it testing?
yeah call it installpkg because that is what it does regardless of the version or what version is already installed. it is no longer misleading, rather it is now covering all three possibilities.

I'd love to have you sign some contracts , the way you think( use your ability to rationalize)it looks like someone can pull the wool over your eyes easily, and you like to try and get everyone to agree with you just so yo can feel right about yourself. or so you will never be wrong, even if you are. denial and projection.
you keep stating you're right and I am wrong in some form or another, your pride is getting the best of you, if I am wrong then the rest of the world is too.

not can be
is...
...



"there's more than one meaning to the word.[upgrade]" you better inform the world then....

rationalize is the attempt to explain or justify (one's own or another's behavior or attitude) with logical, plausible reasons, even if these are not true or appropriate.

So write a new version of upgradepkg that works the way you think it should and move on. This discussion is getting ridiculous.

it is not my distro and I am not going to accept something that is misleading as a truth, and I am not the one that keeps trying to get someone to accept something that is misleading as a truth. I am just stating the facts not trying to defend something that is misleading, deceptive, confusing, deceiving, fallacious, specious, spurious, false.

Nor will I say I accept it or agree with it nor say it is right because it is misleading deceptive, confusing, deceiving, fallacious, specious, spurious, false.

I just know better then to do that for one, and why not just change it to Installpkg so it will no longer be misleading deceptive, confusing, deceiving, misleading deceptive, confusing, deceiving, fallacious, specious, spurious, false.?

and I am the one that is wrong for not accepting something that is not a truth.

Words have different meanings in different contexts. Apparently, "upgrade" does not mean what you thought it did in the context of Slackware. There's nothing misleading or deceiving about it, no matter how many times you feel like writing that word in one sentence. Let's stop beating this dead horse, shall we?

"Active OpenBSD development is known as the -current branch."

"FreeBSD-CURRENT is the “bleeding edge” of FreeBSD development and FreeBSD-CURRENT users are expected to have a high degree of technical skill."

"NetBSD-current is a daily snapshot of the NetBSD development source tree. Because it is a work in progress, it may not be particularly well tested, and it may not even compile."

No, but I am starting to think that you are wasting everyone's times on this.

I, for one, enriched my vocabulary.

This can go two ways, the better one would be to look at who may have started that, then rationalized it in order to justify the why?

What distro has been around the longest?

What is going on here is more then meets the eye.

One misleads another, that other rationalizes it so they can talk themselves into believing it, so it fits onto there belief system, then whenever someone else tries to point this deception out to them, they immediately go onto a state of denial, then starts their rationalizing to not only keep that deception in their own heads, they are now trying to get others to accept this deception as well.


You've never heard of the term, you're only deceiving yourself?
Sure, it starts with the little thing's like this. Then whence the process has been accepted, it can and does lead to bigger thing's.

All that lie has to do is get his foot in the door, whence one lets it in, it then can take root and do its distortion of reality, which is essentially causing one to not only stop looking for the Truth, but to fight against it whenever it presents itself.
And that is exactly what is going on here.

I think you have taken this far enough, if not too far. You accuse Slackware's developer of lying and deceiving, so I suggest strongly you ask a moderator to prune this completely off-topic metaphorical discussion about your perceived issue with upgradepkg into its own separate thread.

I am not , look at my wording, and it the shoe fits wear it, it started with using the word upgrade all with sbotools, I pointed out a truth. that it doesn't upgrade because it will replace another lesser version from the one already installed. that is called down grading, then you and some others choose to deny that truth and came in an attack the truth, then started in on deflecting.

yeah upgradepkg is mis named because it is designed to not upgrade but to install whatever complies to how ever it has to in order for it to be installed regardless of what version of software is already installed. therefore it is not a properly named function.

it was then taken off point, by them that seen I would not accept their deception, which is called deflecting, then you and the others are hating the truth and now are not only accusing me of telling the truth. but telling me to stop telling the truth. what does that say of a person that does that?

you're the one that is accepting the deception not I. just like I pointed out the why behind it. here it is, you're fighting against the truth of what I originally presented by accusing me of being wrong and others are now deflecting trying to make me out to be the bad guy in this and all I did was tell the truth.

what kind of person does that?

We already have installpkg, which will not look at the existing database and will allow you to install multiple versions of the same program. Installing is not the same as upgrading (because it's already installed). But this is not the place to be suggesting new names. As I said, feel free to petition Pat to change it to whatever name you think would better fit, but doing that here is the wrong place.

I've seen your "grammar" (or at least "attention to detail") on this forum. I'm not sure you're the best person to to be signing contracts either. I've managed to make it this far in my life without having someone "pull the wool over my eyes". And I'm not "trying to get everyone to agree with me", rather, I'm trying to open your eyes to a world of English that you obviously aren't aware that exists. Everyone else seems to understand what the word upgrade means in this context.

I flat out said you were right in that last post that upgrading can mean to to take a version of a package and install another one. But it doesn't mean just that. That is where you are wrong.

You covered this in your quoted text!

If the version installed is not the best version, and the better one is an earlier version, it's time to upgrade.

Yup, so continue to rationalize your understanding of the word upgrade. I'm done with this. This is rapidly making me want to finally put you on my ignore list. There's just been so many frustrating threads trying to help you, then there's the ignorance in this thread...

Things will settle if we stop answering to answers: who cares who will have the last word?

Then, maybe the OP will come back?

I think you're wrong. Care to argue? :p

do you know what that is called when someone speaks like that?

it is called CYA

but it you analyze the terms/ words used you have to ask, what is a newer of better version? something that has a higher version number therefore it is still upgrading.

then the version before that , that actually worked better is still called How do I downgrade back to what I had because this newer version is buggy.

the answer most likely to be found is, you can't "they" already over wrote the code. waaaahhhhhh :cry: says the one that does not like the newer version again you are still side tracking.

let me state the oblivious then upgradepkg has no version checking in it, so it allows someone to install whatever no matter what is installed. therefore using just the word upgrade within the function and not indecating it does other then upgrade as well is still misleading.

https://beginnersbook.com/2014/01/c-functions-examples/


want a to do what if's ?

One more post such as this here and I'll report you for abuse.

Stop it. Now. Start your own thread on the horrible naming of the Slackware package tools if you must, but stop polluting this thread with your obsession. It isn't helping the OP at all and is bringing nothing to the issue presented here.

I mentioned a fact so that OP would not be mislead thinking the sbotools upgrade-all function would actually upgrade when it too downgrades, so now there is room for error, and everyone else jumped on me I did not start it, I just showed the facts and defended them, go yell at everyone else for posting in here on this same issue you're being bias .. look it up. end message

Reported. Maybe we'll both be banned, but that's the way it is.

make's you feel like a just man doesn't it? You have now successfully fed your ego using bias and partiality. The facts remain the same. The name is misleading because between the name and the how function is designed to not check for versions of software being installed it is making room for error. All I did was try to point out that fact, and defend it.

Why you trying to shut me up to hide that truth so that bit of deception ( at face value ) can live on?

UPGRADEPKG(8)

NAME
upgradepkg - upgrade Slackware packages.

DESCRIPTION
upgradepkg upgrades a Slackware package from an older version to a newer one. It does this by INSTALLING the new package onto the system, and then REMOVING any files from the old
package that aren't in the new package.


At least man page should be updated I found the name confusing in the past too.

This is NOT the place to be discussing changing the name of upgradepkg. We don't do that. Contact should be made with Pat and he can decide how to handle this.