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
Goal: Examine Package Manager, Focus on Command Line Interface
I am so glad that finally, for the first time,
I can learn Slackware Package Management using Docker.
Here is my report as a new slacker who just landed in slackware land,
my journey using minimal install.
Operating System: Artix (OpenRC )
Window Manager: Herbstluftwm
Since we are going to use docker again,
you can read a common overview here.
Of course you can use virtualization, the issue is distraction.
We need to avoid tendency to focus on GUI tools.
At the same time, limiting the scope to CLI tools.
Most of the time, CLI tools is considered lower level than the GUI one.
Getting Started With Docker
Our first move is, of course attach docker process, as usual.
Slackware does not really have a sophisticated official package management.
Beside slackpkg there are special unoffical tools
to manage your packages such as sbopkg,
slapkg and slackpkgplus.
There are still, other cool command though.
However, I choose not to bloat my minimal install.
Install, Remove, Search, Info, File
We have seen Install in previous example.
How about reinstall ?
We have seen search in action in previous section.
Listing package files can be achieved using /var/log/packages/.
Container: Minimal or Full Install ?
What should I do with this Container ?
How you play with your toy is up to you.
At least we have two choice.
Two kind of toy.
Populate Using Slackware64
Stay with Minimal Install.
The docker image vbatts/slackware
is a slackware minimal install.
Therefore you need to populate with full slackware distribution.
The issue with slackware64 is
my docker container grown from 86.7 MB to 8.64 GB.
Slackware64 has this huge size as a drawback.
For that reason I decice to scrap the container.
I can’t afford huge container,
as I intent to play with other docker container as well.
I will do that when I have my own computer.
But I would never do that again with my docker.
Stay with Minimal Install
With minimal install, I am own my own.
I assume that I know what I am doing.
For binary package come form official repository, it is all alright.
The drawback is you have to prepare toolchain for slackbuild package,
this slackbuild is unofficial, and must be compiled.
I must admit that I know nothing about toolchain.
But here it is what you need based on my experience.
And some other package required
by make when I compile fish
It is not a big deal.
Just be brave to identify what each build need.
D Package Series
You can install D Package Series
as mentioned in installation help:
I remind that I keep my minimal install for learning purpose.
So do not have any plan to install D Package Series.
If storage is not a problem for you,
you can install D Package Series,
or even use full Slackware64 install.
Change mirror is slackware can be done,
by changing the /etc/slackpkg/mirrors.
Here I uncomment local university named kambing.
The result will shown when update.
The repository is already using kambing.
System wide information.
You can query installed packages,
with rather hackish low level slackway as below
This will install a lot of package.
I personally, avoid to use it.
Clean non official repository.
I won’t do this.
The Log File
This is most the forgotten part of package management,
although it is not uncommon to notice messages.
For that reason, I put the recorded event here,
before discussing about any further feature.
Unfortunately, I cannot find any reference about slackpkg log file.
However, there is are some log file for