use 'slackpkg upgrade-all' to keep your system up-to-dated.
This command search for upgraded packages spanning all configured repositories.
use 'slackpkg install-new' (if you use current) to check for new packages.
This command search new packages ONLY in official slackware repository.
the command
slackpkg {install,upgrade,remove,reinstall}
accept:
1) package-name (span all repositories)
2) part of package-name (span all repositories)
3) path of package in repository, for example slackpkg install xap - span all repositories
4a) repository-name, for example slackpkg upgrade alienbob - upgrade packages from specified repository
4b) repository-name, for example slackpkg install ktown - install all packages in ktown repository
5) repository-name:package-name, for example slackpkg install slacky:openjdk - install slacky openjdk even if that repository is not the first in order
6) file:local-file-name (txz/tgz), for example slackpkg install file:mypackage-1.0-noarch-1my.txz - install mypackage even if not defined in slackpkgplus.con; you can optionally specify relative or absolute path
7) file:directory/, for example slackpkg {install|upgrade} file:/root/myrepo/ (do not forget the final '/') - install or upgrade all packages in path (note: 'slackpkg install .' is an alias of 'slackpkg install file:./', but 'slackpkg install ./' is NOT the same alias; search FILE in man slackpkg)
does not forget to read some special instruction from http://taper.alienbase.nl/mirrors/alien-kde/current/latest/ becouse you may need to remove some kde-slackware package. At time:
remove 'ktown:.*' from PKGS_PRIORITY and from REPOPLUS (but not delete related MIRRORPLUS line)
# slackpkg update
# slackpkg upgrade-all
# slackpkg install kde
# slackpkg remove ktown
then delete or comment the related MIRRORPLUS line and then launch:
# slackpkg update
-----
PERSONAL PACKAGES:
If you build yourself some package, you can install these without installpkg, by using slackpkg. That operation help you to track the installation/upgrade and reduce the error margin. You do NOT need to create a your personal repository, generating a gpg-key and all needed metadata any time you build a package; also yo do NOT need to modify you config file and launch slackpkg update.
You can:
1) install/upgrade/reinstall a single package by passing the full file name (optionally add absolute or relative path):
2) install/upgrade/reinstall all file packages in a single directory (does not allow subtree) by passing the directory name following the "/" simbol (optionally absolute or relative path):
# slackpkg install file:/myrepo/
# slackpkg upgrade file:./test/packages/
# slackpkg reinstall .
'.' is an alias of 'file:./', but only that alias exists. slackpkg install ./ or /myrepo/ or ./package.txz generate an error becouse in standard slackpkg you can specify a FILE as input, so in 'slackpkg install ./list.txt' list.txt must to be a plain file containing a list of packages to install (see man slackpkg)
Tip: if you want to use file:/myrepo/ to track your installations and you have lost the original txz/tgz file, you can simply create an empty file; this fools slackpkg+ that only search for file name and not for contents (unless you do not run slackpkg reinstall on these packages ;))
by doing
# touch mypkg1-1.0-noarch-1my.tgz
# touch mysecondpkg-1.1-noarch-2my.txz
where mypkg1 and mysecondpkg are already installed packages, 'slackpkg install .' (or upgrade) does not show you that packages. 'slackpkg reinstall .' DOES show it (so do not continue the installation)