Table of Content
This is a three-parts article. There are few sections here.Part One
- 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 few options to have slackbuild compiled.
Other tools such as
Here we I use
fish as an experiment.
You can use other Slackbuild as well such as
Get the slackbuild. Using the appropriate slackware version.
Get the source code.
Do the compilation process.
Be brave to track error in
whenever you encounter error.
And finally install.
Sometimes (or usually for beginner), error happened while building from source. This step give me better understanding of my system.
You should take a look at the config log for more verbose message.
You can see in that figure above that
we need to install
as the Portable GNU Assembly.
Other case we encounter a more complicated thing,
such as missing file that must be search first.
Here is some example.
This doesn’t look as so bad. Actually searching for these files is fun if you have time.
All you need is patience, and passion.
After manual compilation, we can continue to automatic compilation.
There is this
sbopkg tool to make your life easier.
- Official Site: Building and Installing Packages with sbopkg
Now you are ready to use
But however you need to install
to populate repository data to local.
First Thing First
As long as you prepare toolchain well,
sbopkg is helpful.
The sbopkg Log File
There also unofficial package manager for slackware that emulate Debian apt-get.
slapt-get for binary,
slapt-src for source such as slackbuild.
Dependencies of slapt-get
These packages are required to run
First Thing First
htop install succeed.
ncdu install failed,
ncdu comes from slackbuild.
Since ncdu come from slackbuild repository that needed to be compiled first. We need another tool to manage.
In order to use slackbuild form source,
we can utilize
This time no need to wget,
since we already have
First Thing First
Do update first before doing nay task with any command.
Now we can install
ncdu from slackbuild.
Consider finish reading [ Part Three ]
slpkg and repository.
Thank you for reading
- Docker - Package Management Summary
- Docker - LFS Build
- Docker - Arch ALPM - Part Four
- Docker - Arch ALPM - Part Three
- Docker - Arch ALPM - Part Two
- Docker - Arch ALPM - Part One
- Docker - Debian APT - Part Four
- Docker - Debian APT - Part Three
- Docker - Debian APT - Part Two
- Docker - Debian APT - Part One
- Docker - Slackware Package - Part Three
- Docker - Slackware Package - Part One
- Docker - Fedora DNF - Part Four
- Docker - Fedora DNF - Part Three
- Docker - Fedora DNF - Part Two
- Docker - Fedora DNF - Part One
- Docker - openSUSE Zypper - Part Four
- Docker - openSUSE Zypper - Part Three
- Docker - openSUSE Zypper - Part Two
- Docker - openSUSE Zypper - Part One
- Docker - Void XBPS - Part Two
- Docker - Void XBPS - Part One
- Docker - Gentoo Portage - Part Three
- Docker - Gentoo Portage - Part Two
- Docker - Gentoo Portage - Part One
- Docker - Crux Ports
- Distribution - Debian to Devuan Migration
- Distribution - Manjaro OpenRC to Artix Migration
- Distribution - Mageia 6 Upgrade
- File System - GRUB2 support for BTRFS
- Distribution - openSUSE Tumbleweed First Time Install
- Distribution - Fedora First Time Install
- Distribution - Manjaro OpenRC Issues
- July 2017
- June 2017
- May 2017
- April 2017