aclemons/sbopkg repository overview

⁠sbopkg Docker Image

⁠Quick reference

• Maintained by:

  aclemons⁠

⁠Supported tags and respective Dockerfile links

• latest, slack-15.0⁠ - latest sbopkg installed on slackware stable
• slack-current⁠ - latest sbopkg installed on slackware current

⁠Quick reference (cont.)

• Where to file issues: https://github.com/aclemons/sbopkg-docker/issues⁠

• Supported architectures: amd64, armv7, arm64v8, i386 (varies per Slackware release)

⁠What is sbopkg?

Sbopkg is a command-line and dialog-based tool to synchronise with the SlackBuilds.org ("SBo") repository, a collection of third-party SlackBuild scripts to build Slackware packages.

It is maintained by Willy Sudiarto Raharjo willysr⁠.

⁠How to use

Running sbopkg in a docker container means you always have a clean environment. You probably want to bind mount some directories so that the output ends up on the host. Something like this should get your started:

mkdir -p $HOME/sbopkg/{tmp,sbopkg}
docker run --rm -it -v $HOME/sbopkg/sbopkg:/var/lib/sbopkg/ -v $HOME/sbopkg/tmp:/tmp aclemons/sbopkg

Then build as your normally would with sbopkg:

sbopkg

You can also directly invoke sbopkg/sqg:

docker run --rm -it -v $HOME/sbopkg/sbopkg:/var/lib/sbopkg/ -v $HOME/sbopkg/tmp:/tmp aclemons/sbopkg sbopkg -r

If you want to build i586 or arm packages, you can pass --platform linux/386 or --platform linux/arm in your docker run invocation.

⁠Keeping dependencies

Since the container is clean each time you start it, you won't have your packages installed that you have previously built. If you bind mount the directories mentioned above, you can ask the entrypoint to install any packages found in /tmp. This will emulate the behaviour of having sbopkg on your machine and all the packages installed, but will keep your local machine clean of any build artefacts etc.

docker run --rm -it -e SBOPKG_AUTO_INSTALL=yes -e TERSE=0 -v $HOME/sbopkg/sbopkg:/var/lib/sbopkg/ -v $HOME/sbopkg/tmp:/tmp aclemons/sbopkg sbopkg -k -B -i some-package

⁠Licence

The Docker image creation scripts contained under the repository sbopkg-docker are licensed under the MIT licence.

As with all Docker images, these likely also contain other software which may be under other licences (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licences for all software contained within.