-   Slackware (
-   -   Slackware package upgrades (

simopal6 02-21-2009 03:23 AM

Slackware package upgrades
Today I've had a look at the Slackware security advisories, and decided to upgrade libpng and git.
My doubt is, should I install the new package without removing the old one, or should I remove the old one first?
For example, I've installed the new libpng, now I have both libpng-1.2.27 and 1.2.35.
I'm not sure if I should uninstall the old version, since some programs might be using its shared library. On the other hand, should I worry about disk space usage by old packages?

H_TeXMeX_H 02-21-2009 03:25 AM

You should use 'upgradepkg' to upgrade packages.

Didier Spaier 02-21-2009 03:50 AM

I would not keep old versions.

If you keep it, you stay at risk.

About shared libraries, there should be no problem for applications coming in official Slackware packages as well as applications compiled using a "good" SlackBuild as those provided

So I would use 'upgradpkg', as stated by 'H_TeXMeX_H'.

If you have already installed two different versions, I would 'removepkg' both, then 'installpkg' or 'upgradepkg --install-new -reinstall' the last one.

brianL 02-21-2009 05:45 AM

Use slackpkg. Uncomment your nearest mirror in /etc/slackpkg/mirrors, then run as root:

slackpkg update
slackpkg upgrade-all

This will remove the old, and install the new.

simopal6 02-22-2009 03:15 AM

Thanks to everyone.
Actually, I rarely use precompiled packages, I usually compile libraries and application from source. This is why I'm afraid that some compiled stuff might still depend on the old version of the library. However, I realize that keeping the old libraries makes the upgrade useless...

Edit: anyway, for git, I think there should be no problem if I overwrite the existing installation (maybe I could have trouble if I used GUI for git, but I don't).

All times are GMT -5. The time now is 11:10 AM.