sbotools » documentation

sboconfig

Section: dawnrazor.net (1)
Updated: Pungenday, Discord 45, 3185 YOLD
Index  

NAME

sboconfig - set sbotools configuration options.  

SYNAPSES

sboconfig [-h|-v] [-l] [-c TRUE|FALSE] [-d TRUE|FALSE] [-j #|FALSE] [-p /path|FALSE] [-s /path|/usr/sbo]  

DESCRIPTION

sboconfig is a front-end for managing sbotools configuration options. The sbotools.conf(5) file can also be manually edited; any fields not relevant to sbotools configuration will be ignored.  

OPTIONS

-h|--help
Show help information.
-v|--version
Show version information.
-l|--list
List out current configuration options, including unmodified default configuration options (meaning that if a given option is not set in the sbotools.conf(5) file, the default will be shown for that option). Also shows the flag to sboconfig used to set each option.
-c|--noclean (FALSE|TRUE)
NOCLEAN: If TRUE, then DO NOT clean working directories after building the slackbuild. These are the directories where the source is unpacked and compiled, and where the package is put together in, which are under /tmp/SBo (or $TMP). By default, these directories are removed after building an slackbuild. Setting this option to TRUE causes the working directories to not be cleaned by default. This can be overridden when running sboupgrade(1)/sboinstall(1).
-d|--distclean (FALSE|TRUE)
DISTCLEAN: If TRUE, then DO remove the source code after building the slackbuild. By default, the source code is not removed, and lives under $SBO_HOME/distfiles, which, by default, is /usr/sbo/distfiles. Setting this option to TRUE causes the source code to be removed by default. This can be overridden when running sboupgrade(1)/sboinstall(1).
-j|--jobs (FALSE|#)
JOBS: If numeric (2,5,10, etc), then that number will be fed to the "-j" argument to make when a slackbuild which invokes "make" is run. This only makes sense on multicore systems, where one might set the JOBS to the number of available cores, or half that number, etc.
-p|--pkg-dir (FALSE|/path)
PKG_DIR: If set to a path, packages will be stored at the given location after building and installing. By default, packages are left where they are deposited by slackbuilds, which is typically (probably always) /tmp (or $OUTPUT). If PKG_DIR is FALSE and DISTCLEAN is TRUE (either in sbotools.conf(5) or at sboupgrade/sboinstall runtime), the package will be deleted. If this option is set to a path in the filesystem, the package will be stored in that directory, regardless of any DISTCLEAN option.
-s|--sbo-home (/usr/sbo|/path)
SBO_HOME: If set to a path, this is where the slackbuilds.org tree will live; by default, /usr/sbo will be used. If the tree should live elsewhere, this option can be set to the path where the tree should live. Note that if you set this option after fetching the tree to a different location (such as the default), you will need to fetch the tree again.
-o|--local-overrides (FALSE|/path)
LOCAL_OVERRIDES: If set to a path, any directory name under that path that matches a slackbuild name will be used instead of anything found on SBo. This will even work if it isn't on SBo at all. It still requires all the usual files present in an SBo directory such as README, name.info, and name.SlackBuild.
-V|--slackware-version (FALSE|#.#)
SLACKWARE_VERSION: If set to a version specification, use the SBo repository for that version instead of the one you can find in /etc/slackware-version.
-r|--repo (FALSE|url)
REPO: If set to a url, use that repository instead of the SlackBuilds.org repository for your SLACKWARE_VERSION. Setting this will make the SLACKWARE_VERSION setting redundant. URLs need to either lead to a git repository or an rsync repository. The repository needs to be laid out like the SlackBuilds.org one with a couple of broad categories at the root and under those are subdirectories for each package.
 

EXIT CODES

sboconfig can exit with the following codes:

0: all operations were succesful.

1: a usage error occurred, such as trying to specify invalid options.
6: sboconfig was unable to obtain a required file handle.
 

BUGS

None known, but there may be some. Please report any found to https://github.com/pink-mist/sbotools/issues ; patches are always welcome.  

SEE ALSO

sbocheck(1), sboclean(1), sbofind(1), sboinstall(1), sboremove(1), sbosnap(1), sboupgrade(1), sbotools.conf(5)  

AUTHORS

Jacob Pipkin <j_[at]_dawnrazor_[dot]_net> Luke Williams <xocel_[at]_iquidus_[dot]_org> Andreas Guldstrand <andreas_[dot]_guldstrand_[at]_gmail_[dot]_com>

 

Index

NAME
SYNAPSES
DESCRIPTION
OPTIONS
EXIT CODES
BUGS
SEE ALSO
AUTHORS
This document was created by man2html, using the manual pages.
Time: 16:42:40 GMT, April 28, 2019