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.
|
Quote:
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 |
Quote:
Code:
ACKAGE DESCRIPTION: 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, Code:
--> Deleting empty directory /opt/blender/2.78/ |
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 Code:
+--------------------------+ |
Quote:
hold on let me mess with blender -- brb wow it did screw it up Code:
exit Code:
code to chop it off until it gets the ver numbers code; |
Quote:
Quote:
Incidentally slapt-get (automated upgrade tool) behaves exactly as upgradepkg on that respect :D |
Quote:
or Pat needs to slap-get his butt up in a chair and behind the keyboard and fix that. just kidding Pat. :D |
All times are GMT -5. The time now is 01:02 AM. |