diff options
Diffstat (limited to 'man1')
| -rw-r--r-- | man1/sbocheck.1 | 37 | ||||
| -rw-r--r-- | man1/sboclean.1 | 62 | ||||
| -rw-r--r-- | man1/sboconfig.1 | 100 | ||||
| -rw-r--r-- | man1/sbofind.1 | 75 | ||||
| -rw-r--r-- | man1/sboinstall.1 | 127 | ||||
| -rw-r--r-- | man1/sboremove.1 | 52 | ||||
| -rw-r--r-- | man1/sbosnap.1 | 61 | ||||
| -rw-r--r-- | man1/sboupgrade.1 | 116 |
8 files changed, 0 insertions, 630 deletions
diff --git a/man1/sbocheck.1 b/man1/sbocheck.1 deleted file mode 100644 index c931452..0000000 --- a/man1/sbocheck.1 +++ /dev/null @@ -1,37 +0,0 @@ -.TH sbocheck 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sbocheck - update a local slackbuilds.org tree and check for updates. -.SH SYNAPSES -.P -sbocheck [-h|-v] -.SH DESCRIPTION -.P -sbocheck first updates a previously fetched copy of the slackbuilds.org tree (see sbosnap(1)) and then checks to see if any packages installed from slackbuilds.org have updates, and reports what it finds. Slackbuild's GPG key is required in your keyring. See 'sbosnap import-key' or sbotools.conf for more information. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sboclean(1), sboconfig(1), sbofind(1), sboinstall(1), sboremove(1), sbosnap(1), sboupgrade(1), sbotools.conf(5) -.SH AUTHORS -.P -Jacob Pipkin <j@dawnrazor.net> -.P -Luke Williams <xocel@iquidus.org> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> diff --git a/man1/sboclean.1 b/man1/sboclean.1 deleted file mode 100644 index 83abc5f..0000000 --- a/man1/sboclean.1 +++ /dev/null @@ -1,62 +0,0 @@ -.TH sboclean 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sboclean - clean files left around by sbotools. -.SH SYNAPSES -.P -sboclean [-h|-v] [-dwi] -.SH DESCRIPTION -.P -sboclean is used to clean files left around by sbotools, such as downloaded source files ("distfiles"), or work directories under /tmp/SBo (or $TMP) and, for compat32 installs, under /tmp (or $TMP). Note that if not run with the -i flag, sboclean will remove anything in the distfiles or /tmp/SBo (or $TMP) folders and any /tmp/package-*-compat32 (or $TMP/package-*-compat32) directories with extreme prejudice. One of either -d or -w must be specified for this script to do anything. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.P --d|--dist -.RS -Clean distfiles, by default located at /usr/sbo/distfiles. -.RE -.P --w|--work -.RS -Clean working directories, located, by default under /tmp/SBo and, for compat32 installs, by default, /tmp. -.RE -.P --i|--interactive -.RS -Be interactive; sboclean will ask for confirmation for each item which it thinks should be removed. -.SH EXIT CODES -.P -sboclean can exit with the following codes: -.RS - -0: all operations completed successfully. -.RE -.RS -1: a usage error occurred, such as running sboclean with nothing to clean. -.RE - -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sbocheck(1), sboconfig(1), sbofind(1), sboinstall(1), sboremove(1), sbosnap(1), sboupgrade(1), sbotools.conf(5) -.SH AUTHOR -.P -Jacob Pipkin <j@dawnrazor.net> -.P -Luke Williams <xocel@iquidus.org> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> diff --git a/man1/sboconfig.1 b/man1/sboconfig.1 deleted file mode 100644 index e8c9a35..0000000 --- a/man1/sboconfig.1 +++ /dev/null @@ -1,100 +0,0 @@ -.TH sboconfig 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sboconfig - set sbotools configuration options. -.SH SYNAPSES -.P -sboconfig [-h|-v] [-l] [-c TRUE|FALSE] [-d TRUE|FALSE] [-j #|FALSE] [-p /path|FALSE] [-s /path|/usr/sbo] -.SH DESCRIPTION -.P -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. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.P --l|--list -.RS -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. -.RE -.P --c|--noclean (FALSE|TRUE) -.RS -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). -.RE -.P --d|--distclean (FALSE|TRUE) -.RS -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). -.RE -.P --j|--jobs (FALSE|#) -.RS -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. -.RE -.P --g|--gpg-key (FALSE|KEY_ID) -.RS -GPG_KEY: Use GPG to verify the slackbuilds.org tree on download using this GPG key. The default is configured to slackbuild.org's key 'D3076BC3E783EE747F09B8B70368EF579C7BA3B6'. You may want to disable if you are using Slackware current. Set to FALSE to disable. -.RE -.P --p|--pkg-dir (FALSE|/path) -.RS -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. -.RE -.P --s|--sbo-home (/usr/sbo|/path) -.RS -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. -.RE -.P --o|--local-overrides (FALSE|/path) -.RS -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. -.RE -.P --V|--slackware-version (FALSE|#.#) -.RS -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. -.RE -.P --r|--repo (FALSE|url) -.RS -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. -.RE -.SH EXIT CODES -.P -sboconfig can exit with the following codes: -.RS - -0: all operations were succesful. -.RE -.RS -1: a usage error occurred, such as trying to specify invalid options. -.RE -.RS -6: sboconfig was unable to obtain a required file handle. -.RE -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sbocheck(1), sboclean(1), sbofind(1), sboinstall(1), sboremove(1), sbosnap(1), sboupgrade(1), sbotools.conf(5) -.SH AUTHORS -.P -Jacob Pipkin <j@dawnrazor.net> -.P -Luke Williams <xocel@iquidus.org> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> diff --git a/man1/sbofind.1 b/man1/sbofind.1 deleted file mode 100644 index e5aaace..0000000 --- a/man1/sbofind.1 +++ /dev/null @@ -1,75 +0,0 @@ -.TH sbofind 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sbofind - search slackbuilds.org tree for a given name -.SH SYNAPSES -.P -sbofind [-h|-v] [-ir] search_term -.SH DESCRIPTION -.P -sbofind searches the names of all slackbuilds for a given term. It reports back any slackbuilds found along with the path for each. This is equivalent to running "cd /usr/ports; make search name=$search_term display=name,path" on a FreeBSD system. If the repository includes a TAGS.txt file, that will be used to find more results as well. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.P --e|--exact -.RS -Only exact matching. -.RE -.P --t|--no-tags -.RS -Exclude tags from search. -.RE -.P --i|--info -.RS -Show the contents of the .info file for each slackbuild found. -.RE -.P --r|--readme -.RS -Show the contents of the README file for each slackbuild found. -.RE -.P --q|--queue -.RS -Show the build queue for each slackbuild found. -.RE -.SH EXIT CODES -.P -sbofind can exit with the following exit codes: -.RS - -0: all operations were succesful. -.RE -.RS -1: a usage error occured, ie sbofind was ran with nothing to find. -.RE -.RS -6: sbofind was unable to obtain a required file handle. -.RE -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sbocheck(1), sboclean(1), sboconfig(1), sboinstall(1), sboremove(1), sbosnap(1), sboupgrade(1), sbotools.conf(5) -.SH AUTHORS -.P -Jacob Pipkin <j@dawnrazor.net> -.P -Luke Williams <xocel@iquidus.org> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> diff --git a/man1/sboinstall.1 b/man1/sboinstall.1 deleted file mode 100644 index 796d45a..0000000 --- a/man1/sboinstall.1 +++ /dev/null @@ -1,127 +0,0 @@ -.TH sboinstall 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sboinstall - install slackbuilds -.SH SYNAPSES -.P -sboinstall [-h|-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-NrRip] [--create-template FILE] sbo_name (sbo_name) -sboinstall [-h|-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-NRip] --use-template FILE -.SH DESCRIPTION -.P -sboinstall is used to install SBos. If the -r flag is NOT specified, sboinstall will pull the list of requirements from the .info file for any specified slackbuild. If such a list exists, sboinstall will look to see whether or not those requirements are already installed, and if not, it will ask whether or not it should attempt to install them first. This is recursive, so that ordering happens correctly. sboinstall will refuse to handle circular requirements. sboinstall will attempt to note groupadd and useradd commands in README files and offer to run those first. If the README appears to document options of the KEY=value form, sboinstall will offer the opportunity to set options. -.P -sboinstall will attempt to download the sources from the DOWNLOAD or DOWNLOAD_x86_64 variables in the .info file. If such a download fails or the file can't be verified, it'll attempt to download the file from ftp://slackware.uk/sbosrcarch/ instead. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.P --c|--noclean (FALSE|TRUE) -.RS -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. This option leaves those directories in place. This can be set as default via the sboconfig(1) command. Also see sbotools.conf(5). This option overrides the default. -.RE -.P --d|--distclean (FALSE|TRUE) -.RS -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; this option can be set as default via the sboconfig(1) command. See also sbotools.conf(5). This option overrides the default. -.RE -.P --i|--noinstall -.RS -Do not actually install the package created at the end of the build process. So, the slackbuild will be run, and the package will be left in /tmp (or $OUTPUT), or in $PKG_DIR if so defined (see sboconfig(1) and sbotools.conf(5)). -.RE -.P --j|--jobs (FALSE|#) -.RS -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. -.RE -.P --p|--compat32 -.RS -Create a -compat32 package instead of a normal x86_64 package on multilib x86_64 systems. This requires /usr/sbin/convertpkg-compat32; this can at least be obtained from AlienBob's compat32-tools package - see http://alien.slackbook.org/blog/. Note that this may or may not be foolproof, and is not supported by anyone; not me, not AlienBob, not Slackware, etc. I recommend using this with the -i option so that the created package can be inspected prior to installation. Note this option is kept for posterity, but lacked good support, it is best avoided. -.RE -.P --r|--nointeractive -.RS -Skip viewing of the README and the yes or no question which accompanies it. Anytime sboinstall is run, the first thing the command will attempt to do is show you the README for a given slackbuild and ask whether or not you wish to proceed; this option skips the README and bypasses the question. This also disables dependency resolution, since you have no way of confirming which dependencies you actually want to install. If multiple slackbuilds are specified, this option bypasses them all. -.RE -.P --R|--norequirements -.RS -This option causes sboinstall to skip requirement handling, but still show the README and prompt the user to proceed. -.RE -.P ---reinstall -.RS -This option asks if we should reinstall anything among the requirements that is already installed. -.RE -.P ---create-template (FILE) -.RS -Create a template for the SlackBuilds including any optional commands or build options that you wish to set and store this in the specified FILE. -.RE -.P ---use-template (FILE) -.RS -Use a template file and let it specify all the build options and optional commands to be used. This also enables the --nointeractive flag. -.RE -.SH EXIT CODES -.P -sboinstall can exit with the following exit codes: -.RS - -0: all operations were succesful. -.RE -.RS -1: a usage error occured, such as specifying invalid options. -.RE -.RS -3: a .SlackBuild exited non-zero. -.RE -.RS -4: unable to md5sum verify an SBo's source file(s). -.RE -.RS -5: unable to download an SBo's source file(s). -.RE -.RS -6: unable to obtain a required file handle. -.RE -.RS -7: unable to get required info from the SBo's .info file. -.RE -.RS -8: unable to unset the exec-on-close bit on a temporary file. -.RE -.RS -9: multilib hasn't been setup (where required). -.RE -.RS -10: convertpkg-compat32 exited non-zero. -.RE -.RS -11: the convertpkg-compat32 script can't be found (where required). -.RE -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sboremove(1), sbosnap(1), sboupgrade(1), sbotools.conf(5) -.SH AUTHORS -.P -Jacob Pipkin <j@dawnrazor.net> -.P -Luke Williams <xocel@iquidus.org> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> diff --git a/man1/sboremove.1 b/man1/sboremove.1 deleted file mode 100644 index d57fbdb..0000000 --- a/man1/sboremove.1 +++ /dev/null @@ -1,52 +0,0 @@ -.TH sboremove 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sboremove - remove packages installed from slackbuilds -.SH SYNAPSES -.P -sboremove [-h|-v] [-a] sbo_name -.SH DESCRIPTION -.P -sboremove is used to remove packages installed from slackbuilds. It pulls the list of requirements from the .info file for any specified slackbuild. If such a list exists, sboremove will look to see whether or not those requirements are installed. Those that are will then be checked to see whether they are requirements of other packages also installed. If a package is no longer required, or the -a flag is specified sboremove will ask whether or not it should also remove it from the system. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.P --a|--alwaysask -.RS -Always ask to remove requirements, even those required by other packages currently installed (ignored by default) -.RE -.SH EXIT CODES -.P -sboremove can exit with the following codes: -.RS - -0: all operations completed successfully. -.RE -.RS -1: a usage error occurred, such as running sboremove with nothing to remove. -.RE -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sboinstall(1), sbosnap(1), sboupgrade(1), sbotools.conf(5) -.SH AUTHORS -.P -Luke Williams <xocel@iquidus.org> -.P -Jacob Pipkin <j@dawnrazor.net> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> diff --git a/man1/sbosnap.1 b/man1/sbosnap.1 deleted file mode 100644 index 5de6bcc..0000000 --- a/man1/sbosnap.1 +++ /dev/null @@ -1,61 +0,0 @@ -.TH sbosnap 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sbosnap - slackbuilds.org tree fetch and update command. -.SH SYNAPSES -.P -sbosnap [-h|-v] (fetch|import-key|update) -.SH DESCRIPTION -.P -sbosnap is used to download and update a local copy of the slackbuilds.org tree, minus the .tar.gz{,.asc} files. Note that sbocheck(1) will also update the tree, and will then also check for updated slackbuilds. rsync is used for both operations. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.SH COMMANDS -.P -fetch -.RS -Download a local copy of the slackbuilds.org tree. The copy will be downloaded to the SBO_HOME setting (see sboconfig(1) and sbotools.conf(5)), which, by default, is /usr/sbo -.RE -.P -update -.RS -Update a previously fetch'd copy of the slackbuilds.org tree. -.RE -.SH EXIT CODES -.P -sbosnap can exit with the following codes: -.RS - -0: all operations completed successfully. -.RE -.RS -1: a usage error occurred, such as running sbosnap with no command. -.RE -.RS -5: error downloading from the repository. -.RE -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sboinstall(1), sboremove(1), sboupgrade(1), sbotools.conf(5) -.SH AUTHORS -.P -Jacob Pipkin <j@slackcoder.server.ky> -.P -Luke Williams <xocel@iquidus.org> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> diff --git a/man1/sboupgrade.1 b/man1/sboupgrade.1 deleted file mode 100644 index e96072c..0000000 --- a/man1/sboupgrade.1 +++ /dev/null @@ -1,116 +0,0 @@ -.TH sboupgrade 1 "Pungenday, Chaos 28, 3191 YOLD" "sbotools 2.8.0" sbotools2 -.SH NAME -.P -sboupgrade - install or upgrade slackbuilds -.SH SYNAPSES -.P -sboupgrade [-h|-v] [-c TRUE|FALSE] [-d TRUE|FALSE] [-j #|FALSE] [-fNrRiz] --all|sbo_name (sbo_name) -.SH DESCRIPTION -.P -sboupgrade is used to upgrade packages installed from slackbuilds. If the -r flag is NOT specified, sboupgrade will pull the list of requirements from the .info file for any specified slackbuild. If such a list exists, sboupgrade will look to see whether or not those requirements are already installed, and if not, it will ask whether or not it should attempt to install them first. This is recursive, so that ordering happens correctly. sboupgrade will refuse to handle circular requirements. sboupgrade will also note groupadd and useradd commands in README files and offer to run those first. If the README documents options of the KEY=value form, sboupgrade will offer the opportunity to set options. If --all is supplied it will try to upgrade everything that sbocheck(1) reports. -.P -sboupgrade will attempt to download the sources from the DOWNLOAD or DOWNLOAD_x86_64 variables in the .info file. If such a download fails or the file can't be verified, it'll attempt to download the file from ftp://slackware.uk/sbosrcarch/ instead. -.SH OPTIONS -.P --h|--help -.RS -Show help information. -.RE -.P --v|--version -.RS -Show version information. -.RE -.P --c|--noclean (FALSE|TRUE) -.RS -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. This option leaves those directories in place. This can be set as default via the sboconfig(1) command. Also see sbotools.conf(5). This option overrides the default. -.RE -.P --d|--distclean (FALSE|TRUE) -.RS -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; this option can be set as default via the sboconfig(1) command. See also sbotools.conf(5). This option overrides the default. -.RE -.P --f|--force -.RS -Force an upgrade, even if the installed version is equal to or less than the slackbuilds.org version. -.RE -.P --i|--noinstall -.RS -Do not actually install the package created at the end of the build process. So, the slackbuild will be run, and the package will be left in /tmp (or $OUTPUT), or in $PKG_DIR if so defined (see sboconfig(1) and sbotools.conf(5)). -.RE -.P --j|--jobs (FALSE|#) -.RS -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. -.RE -.P --r|--nointeractive -.RS -Skip viewing of the README and the yes or no question which accompanies it. Anytime sboupgrade is run, the first thing the command will attempt to do is show you the README for a given slackbuild and ask whether or not you wish to proceed; this option skips the README and bypasses the question. This also disables dependency resolution, since you have no way of confirming which dependencies you actually want to install. If multiple slackbuilds are specified, this option bypasses them all. -.RE -.P --z|--force-reqs -.RS -When used in combination with the -f option, to force an update even if it would not constitute an update, this will cause sboupgrade to also rebuild all of that slackbuild's requirements. Normally with -f, only the slackbuild(s) specified, and any requirements not already installed, will be rebuilt. This allows for recursive upgrades, among other things. -.RE -.P ---all -.RS -You can specify --all instead of an sbo_name to upgrade all the packages sbocheck(1) reports. -.RE -.SH EXIT CODES -.P -sboupgrade can exit with the following exit codes: -.RS - -0: all operations were succesful. -.RE -.RS -1: a usage error occured, such as specifying invalid options. -.RE -.RS -3: a .SlackBuild exited non-zero. -.RE -.RS -4: unable to md5sum verify an SBo's source file(s). -.RE -.RS -5: unable to download an SBo's source file(s). -.RE -.RS -6: unable to obtain a required file handle. -.RE -.RS -7: unable to get required info from the SBo's .info file. -.RE -.RS -8: unable to unset the exec-on-close bit on a temporary file. -.RE -.RS -9: multilib hasn't been setup (where required). -.RE -.RS -10: convertpkg-compat32 exited non-zero. -.RE -.RS -11: the convertpkg-compat32 script can't be found (where required). -.RE -.SH BUGS -.P -None known, but there may be some. Please report any found to slackcoder@server.ky ; patches are always welcome. -.SH SEE ALSO -.P -sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sboinstall(1), sboremove(1), sbosnap(1), sbotools.conf(5) -.SH AUTHORS -.P -Jacob Pipkin <j@dawnrazor.net> -.P -Luke Williams <xocel@iquidus.org> -.P -Andreas Guldstrand <andreas.guldstrand@gmail.com> -.SH MAINTAINER -.P -Slack Coder <slackcoder@server.ky> |