Slackpkg does not resolve dependencies between packages, like rpm from Fedora and open SUSE.Only third-party applications, such as slapt-get, have an automated package relation management.
After upgrading the packages, don't forget to edit your /etc/file accordingly and run: to inform the bootloader about the kernel upgrade; or use the tool of your choice to update and reinstall the bootloader. This will copy the new kernel and if applicable the to the correct subdirectory in /boot/efi First it will ask if you wish to "Install ELILO on the EFI System Partition". Then it asks if you want to "install a boot menu entry".
If you just want to boot into Salix, it is ok to choose yes for this, but if you are using r EFInd or grub to multi-boot, select no; the existing configuration should continue to work, giving you the same options as before.
Adding dependency information requires no modification to the packages themselves. Several scripts are available to generate the PACKAGES. The file format used by Patrick Volkerding is extended by adding a few extra lines per package.
slapt-get then parses this file during source downloads.
It was designed to make a Slackware system administrator's job easier by allowing routine package management tasks to be accomplished in a single command.
slackpkg does not replace the Slackware package management tools such as installpkg and upgradepkg; rather it uses them.
Download the corresponding Slackware current packages for your architecture from any Slackware current mirror, such as In the case of that mirror, the packages for a 32-bit system are all in this directory: If you have a 64-bit system, change slackware to slackware64: Download the packages with a browser, or move to the directory where you will put them and fetch with wget: ... If you have switched to the kernel-generic package instead of the default kernel-huge package, don't forget to recreate the file which will be needed for booting your upgraded system.
If you're still using the default kernel-huge package, an initrd is not needed anyway and you needn't be concerned about it.
Slpkg makes it easier to maintain groups of machines without having to manually update.
Slpkg works in accordance with the standards of the organization to builds packages.
I keep some servers on current and others, the ones I consider critical, on 11.0: Since version 11.0 has just come out there won't be many updates right away, so don't expect much at first.