Upgrading multilib packages
Hi,
I recently downloaded and installed 32bit compatibility libraries and the glibc/gcc packages from alienbobs site. I added "[0-9]+alien" to my /etc/slackpkg/blacklist like the page suggested so slackpkg wouldn't replace them. This leads me to one question, how would one go about upgrading these packages/libraries in the future if needed? |
You shouldn't need to upgrade any software unless absolutely necessary, often what you can do is check the version number on the Slackware FTP against the Multilib packages and only get the multilib package if there is an update.
|
Hello,
Quote:
multilibpkg is dedicated to the management (install, check-updates, upgrade, ...) of the 64-bit part of the multilib (ie the multilib version of packages glibc*, gcc*, and, the package compat32-tools), while compat32pkg is dedicated to the management (install, check-updates, upgrade, ...) of the 32-bit part of the multilib (ie the 32-bit compatibility layer) and a bit more. For example to list the available updates for the 32-bit compatibility layer (on slackware-13.37), you're going to use compat32pkg this way : Code:
$ compat32pkg --mirror @WorldWide-13.37 --list-updates layer-32 Code:
$ compat32pkg --mirror @WorldWide-13.37 --upgrade layer-32 Cheers. -- SeB |
Agree, Multilibpkg and Compat32pkg make life simple. I use them both.
Thanks SeB! |
The way I do it is I keep a local mirror of AlienBob's stuff with rsync and just use
upgradepkg. |
Hello,
Quote:
fixes related to some of these packages, and all of the packages that could have been added to the 32-bit layer. For example, in case of Slackware64-13.0, you will miss the following : Code:
bzip2 1.0.6 build 1_slack13.0 Cheers. -- SeB |
Quote:
|
Quote:
Thanks! |
All times are GMT -5. The time now is 07:59 PM. |