sboupgrade

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXIT CODES
BUGS
SEE ALSO
AUTHORS
MAINTAINER

NAME

sboupgrade - install or upgrade SlackBuilds

SYNOPSIS

sboupgrade [-h|-v]

sboupgrade [-c TRUE|FALSE] [-d TRUE|FALSE] [-j #|FALSE] \
           [-b TRUE|FALSE] [-S TRUE|FALSE] [-fiprz] \ \--all\|sbo_name (sbo_name)

DESCRIPTION

sboupgrade is used to upgrade SlackBuilds. If the -r flag is not specified, sboupgrade pulls the list of requirements from the info file for any specified SlackBuild. This is a recursive operation over all dependencies. sboupgrade offers to install any non-installed dependencies in the build queue, taking blacklisted scripts and optional dependency specifications in sbotools.hints(5) into account. If circular dependencies are detected, the script exits with an error message.

README files are parsed for groupadd and useradd commands, and sboupgrade offers to run them prior to building. If the README is judged to document options in KEY=VALUE form, a prompt for setting options appears. Any build options, whether passed interactively or in a template, are saved to /var/log/sbotools when the SlackBuild runs.

Please note that saved build options are not displayed when CLASSIC is set to TRUE; if STRICT_UPGRADES is TRUE, upgrades are only performed for non-override packages if the version or build number is apparently higher. See sboconfig(1) or sbotools.conf(5).

sboupgrade attempts to download the sources from the DOWNLOAD or DOWNLOAD_x86_64 variables in the info file. If either the download or the md5sum check fails, a new download is attempted from ftp://slackware.uk/sbosrcarch/ as a fallback measure. The --all flag may be passed to upgrade all eligible SlackBuilds simultaneously.

sboupgrade verifies the local repository with gpg if GPG_VERIFY is TRUE. Only rsync repositories can be verified on Slackware 14.0 and Slackware 14.1.

If an invalid configuration is detected in /etc/sbotools/sbotools.conf, the script exits with a diagnostic message.

OPTIONS

-h|--help

Show help information.

-v|--version

Show version information.

-b|--build-ignore (FALSE|TRUE)

If TRUE, do not perform upgrades unless the version number differs. By default, upgrades also occur when the build number differs. This setting and --force are not the same; --force initiates upgrades even if the build number is unchanged. This overrides the BUILD_IGNORE setting in sbotools.conf(5).

-c|--noclean (FALSE|TRUE)

If TRUE, do not clean working directories after building. These are the build and package-(sbo) directories under /tmp/SBo (or $TMP). Cleaning these directories can be set as default via the sboconfig(1) command. See also sbotools.conf(5). This option overrides the default.

-d|--distclean (FALSE|TRUE)

If TRUE, then remove the source archives after building. They are retained in md5sum-designated directories under SBO_HOME/distfiles by default. The package archive (in /tmp by default) is also removed. This option can be set as default via the sboconfig(1) command. See also sbotools.conf(5). This option overrides the default.

-f|--force

Force an upgrade, even if the installed version and build number are equal to the SlackBuilds.org version.

-i|--noinstall

Do not install the package at the end of the build process. It is left in /tmp (or $OUTPUT) if DISTCLEAN is FALSE. Packages are retained in PKG_DIR if so defined regardless of DISTCLEAN. See sboconfig(1) and sbotools.conf(5).

-j|--jobs (FALSE|#)

If numerical, pass to the -j argument when a SlackBuild invoking make is run.

-p|--compat32

Create a -compat32 package on multilib x86_64 systems. This requires the compat32-tools package by Eric Hameleers. Please note that this operation is not necessarily foolproof, and is unsupported by anyone in principle. As a best practice, --compat32 should be combined with --noinstall so that the contents of the package can be inspected prior to installation. If the base package and compat32 package are to be built at the same time, ensure that the DISTCLEAN option is set to FALSE. GitHub Issues are welcome in case of unexpected failure.

-r|--nointeractive

Bypass all user prompts and all dependency resolution for the requested SlackBuilds. Unless it is obvious that dependency resolution and build options are not required, this option should not be used with sboupgrade.

-S|--strict-upgrades (FALSE|TRUE)

If TRUE, only perform upgrades if the incoming version or build number is higher. This has no effect scripts in the local overrides directory. This option can be set as default via sboconfig(1). See also sbotools.conf(5). This option overrides the default.

-z|--force-reqs

In the same vein as --force, upgrade the SlackBuild and its dependencies, even if upgrades are not required. Incompatible with --nointeractive.

--all

Upgrade all installed SlackBuilds that are eligible for upgrades. This takes the BUILD_IGNORE setting into account. See sboconfig(1) and sbotools.conf(5). Please note that SlackBuilds installed from a LOCAL_OVERRIDES directory are upgraded only if the version or build number from this directory varies.

EXIT CODES

sboupgrade can exit with the following codes:

0: all operations were succesful.
1: a usage error occured, such as specifying invalid options.
3: a SlackBuild exited non-zero.
4: unable to md5sum verify the source file(s).
5: unable to download the source file(s).
6: unable to obtain a required file handle.
7: unable to get required info from the info file.
8: unable to unset the exec-on-close bit on a temporary file.
9: multilib has not been set up (where required).
10: convertpkg-compat32 exited non-zero.
11: the convertpkg-compat32 script cannot be found (where required).
12: interrupt signal received.
13: circular dependencies detected.

BUGS

None known. If found, Issues and Pull Requests to https://github.com/pghvlaans/sbotools/ are always welcome.

AUTHORS

Jacob Pipkin <j (at) dawnrazor (dot) net>

Luke Williams <xocel (at) iquidus (dot) org>

Andreas Guldstrand <andreas (dot) guldstrand (at) gmail (dot) com>

MAINTAINER

K. Eugene Carlson <kvngncrlsn (at) gmail (dot) com>