This is one topic of a package management diversity series.
This is a three-parts article. There are few sections here.
- Preparing Docker
- IRSIF: slackpkg install, removepkg, Query Search, Show Info, List File
- Container: Slackware64, Minimal Install, Package Series
- System Wide: Installed Packages
- History: The Log File
- No Dependency: Example, slpkg deps-status
- Hold: Blacklist
- Using slackbuild, manual compilation, and installpkg
- Using sbopkg, automatic compilation
- Using slapt-get: Reading, Install, Dependencies, Update, Upgrade, Install, Show Info
- Using slapt-src: Update, Install
- Install slpkg: Dependency, Install, No certificate
- Using slpkg: Documentation, Update, Install, The Log File
- Repository: List, Configuration, Enable, List Package, Install Package
There are still other topic uncovered here
I have been wondering how to add other repository,
And I found this
Now you can install
slpkg using any method you like.
My first attempt, is always failure as usual.
If you encounter this error, you need to install
Now you should be ready.
slpkg in Slackware,
remind me of
dpkg in Debian.
We can manage repository very nicely using
Unfortunately installation failed, we need to solve some dependency first.
And install again. Do the installation command over again.
Mission accomplished, Now I can
You are freely to try other package other than
The slpkg Log File
We can utilize
slpkg to manage repository in Slackware
You can edit directly to enable repository.
Alternatively you can use interactive dialog to enable repository.
Do not forget to update as usual.
Now we can install openbox package from alien repository
but without openbox dependency.
It is said that “Slackware does not resolve dependency”.
I haven’t got enough experience about this situation.
I simply do not understand what it means.
I guess I have to learn slackware more.
Thank you for reading