slackrepo (8)


slackrepo - automated SlackBuild package building and repository maintenance


Exit Status
See Also


slackrepo build [OPTIONS] [ITEM...]
slackrepo rebuild [OPTIONS] [ITEM...]
slackrepo update [OPTIONS] [ITEM...]
slackrepo remove [OPTIONS] ITEM...
slackrepo revert [OPTIONS] ITEM...
slackrepo lint [OPTIONS] [ITEM...]


slackrepo build
  Builds packages from an input repository of SlackBuilds (for example, a git clone of, and then stores them in a package repository. 'add' is accepted as a synonym of 'build'.
slackrepo rebuild
  Rebuilds packages that are already in the package repository.
slackrepo update
  Builds, rebuilds and removes packages in the package repository, according to changes in the SlackBuild repository.
slackrepo remove
  Removes packages from the package repository.
slackrepo revert
  Moves packages from the backup repository into the package repository, and packages from the package repository into the backup repository. 'restore' is accepted as a synonym of 'revert'.
slackrepo lint
  Performs quality tests on source download URLs and source files, SlackBuilds, and packages.
ITEM An item specifies a directory or a SlackBuild file in the SlackBuild repository, and/or (in the update, remove and revert commands only) formerly in the SlackBuild repository. Shell-style globs (wildcards) are allowed. If no items are specified, all directories in the SlackBuild repository are processed (except in the remove and revert commands, where it is mandatory to specify the items to be removed).


  Use the SlackBuild and package repository identified by ID. The filestore locations of the SlackBuild and package repositories are defined in the configuration file /etc/slackrepo/slackrepo_ID.conf, where ID is an identifier for the repositories. The default repository ID is SBo. For details, see slackrepo.conf(5) .
--dry-run Builds and rebuilds will be performed, and removes and reverts will be checked, but no changes will be made to the package repository. This option conflicts with --install. This option has no effect with the lint command.
--install Built, rebuilt and updated packages will be installed on the host system. This results in a "queue" style build, and packages may not be 100% clean of unexpected dependencies. The default is for packages not to be installed. This option conflicts with --dry-run, and has no effect with the remove, revert and lint commands.
--chroot Construct and use a temporary chroot environment for each build process. (Requires a Linux 3.18+ kernel with overlayfs.) This option has no effect with the remove, revert and lint commands.
--lint With the build, rebuild and update commands, the source files and URLs, SlackBuild files, and any built packages will be subjected to quality tests; these tests are the same as the tests performed by the lint command. With the remove, revert and lint commands, this option has no effect.
-v, --verbose
  Display the output of each build process on the console during execution. If --verbose or -v is specified multiple times, it is equivalent to --very-verbose.
-vv, --very-verbose
  Forces make and cmake to produce more verbose compilation output when it is called by a SlackBuild. This option implies --verbose.
  On exit, keep all temporary files in $TMP and $TMPDIR, for debugging purposes.
  Pass coloured output from cmake, clang, git, gcc-4.9, mono, waf etc. to standard output if standard output is a terminal console (--color=auto), or pass colour unconditionally (--color=always), or do not pass colour (--color=no). The default is --color=auto. The --color option is effective only if --verbose is specified. '--colour' is accepted as a synonym of '--color'.
  Adjust the niceness of the build process by integer N. The default is 5 (like distcc).


0 all operations succeeded or only warnings were issued
1 one or more operations failed
2 command usage error
3 config or setup error
4 internal error, please report a bug


The behaviour of slackrepo is affected by the following environment variables:


Each of these environment variables overrides the corresponding configuration variable in the file /etc/slackrepo/slackrepo_ID.conf or ~/.slackreporc. For details, see slackrepo.conf(5).


The MAKEFLAGS variable is passed to each SlackBuild. Its value will be augmented by the value of NUMJOBS, so '-j' should not be specified in MAKEFLAGS.


slackrepo uses the directory specified by TMPDIR (default /tmp) for its own temporary files. (However, SlackBuilds use the directory specified by TMP, not TMPDIR.)


Each of these environment variables can be used to set the default for the corresponding control argument. They override the corresponding configuration variables in the file /etc/slackrepo/slackrepo_ID.conf or ~/.slackreporc. For details, see slackrepo.conf(5).


  This file defines the configuration variables for the SBo repository; see slackrepo.conf(5).
  This file can optionally be created to define the default repository ID and override configuration variables set in /etc/slackrepo/slackrepo_ID.conf; see slackrepo.conf(5).
  This directory contains the hintfiles for the SBo repository; see slackrepo.hint(5).


For best results, slackrepo is intended to be run on a "clean" standard Slackware environment (like a "build box" or a virtual machine), with a full installation of Slackware and no additional packages (or very few). You can then use the package repository to install the packages on other hosts (e.g. with slackpkg+).

Packages are updated or rebuilt if required; for example, if a package is being built, its dependencies will be updated and/or rebuilt if they are out-of-date. A package is out-of-date if:

the git revision in the directory containing the SlackBuild has changed since the package was built
the directory containing the SlackBuilds has untracked/uncommited files (i.e., "git is dirty") and they are newer than the package
the hintfile has changed since the package was built
any of its direct dependencies has been updated since the package was built
the version of Slackware has changed since the package was built

Changes in the SlackBuilds directory are classified as "updates", which will cause directly depending items to be rebuilt. Other changes are classified as "rebuilds" and do not cause depending items to be rebuilt. For example, ffmpeg depends on x264, and transcode depends on ffmpeg. If x264 is updated, ffmpeg will be rebuilt, but transcode will not be rebuilt. If x264 is rebuilt, ffmpeg will not be rebuilt. If ffmpeg is updated, transcode will be rebuilt.

When a package is rebuilt, and when a package is updated but its version is unchanged, the BUILD number in the package repository is always incremented (and the BUILD number in the SlackBuild file is ignored).

slackrepo is not affiliated with, or endorsed by, the Project or Slackware. The author thanks those projects for their continuing generosity to the community. Slackware® is a registered trademark of Patrick Volkerding.


Build the whole SBo repository (you will need about four days and 80Gb of disk space):

# slackrepo build

Build shotwell, with all its dependencies:

# slackrepo build shotwell

Build and install shotwell and all its dependencies (this will NOT be a clean build):

# slackrepo build --install shotwell

Remove grass (note, its dependencies and dependers will not be removed):

# slackpkg remove grass

Restore the backed-up grass packages (note, you can use this to 'undelete' packages that were removed in error):

# slackpkg revert grass

Update all the academic/ packages in your package repository for SBo's latest changes:

# slackrepo update academic

Do a "dry run" update of all your SBo packages, with verbose messages:

# slackrepo update --dry-run -v

Test-build colord (in the csb repo), with output from the build displayed on the console; do not store the built package:

# slackrepo build -v --repo=csb --lint --dry-run colord


slackrepo.conf(5), slackrepo.hint(5), installpkg(8), upgradepkg(8), removepkg(8), pkgtool(8), slackpkg(8).

slackrepo-0.2.0 SLACKREPO (8) 2015-04-12