aboutsummaryrefslogtreecommitdiff
path: root/man1/sboupgrade.1
diff options
context:
space:
mode:
Diffstat (limited to 'man1/sboupgrade.1')
-rw-r--r--man1/sboupgrade.111
1 files changed, 8 insertions, 3 deletions
diff --git a/man1/sboupgrade.1 b/man1/sboupgrade.1
index 3544455..e5bde03 100644
--- a/man1/sboupgrade.1
+++ b/man1/sboupgrade.1
@@ -1,13 +1,13 @@
-.TH sboupgrade 1 "Prickle-Prickle, the 25th day of Bureaucracy in the YOLD 3178" "sbotools 0.8 fnord" dawnrazor.net
+.TH sboupgrade 1 "Boomtime, Bureaucracy 28, 3178 YOLD" "sbotools 0.8 fnord" dawnrazor.net
.SH NAME
.P
sboupgrade - install or upgrade slackbuilds
.SH SYNAPSES
.P
-sboupgrade [-h] [-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-f] [-N] [-r] [-R] [-i] sbo_name (sbo_name)
+sboupgrade [-h] [-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-f] [-N] [-r] [-R] [-i] [-w] 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 attempt to grok a list of requirements in the README for a given 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. Note that this method is FAR from foolproof, which is why this does not happen if the README is bypassed. 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.
+sboupgrade is used to upgrade packages installed from slackbuilds. If the -r flag is NOT specified, sboupgrade will attempt to grok a list of requirements in the README for a given 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. Note that this method is FAR from foolproof, which is part of the reason this does not happen if the README is bypassed. 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 such options.
.SH OPTIONS
.P
@@ -59,6 +59,11 @@ Skip viewing of the README and the yes or no question which accompanies it. Anyt
.RS
This option causes sboupgrade to skip requirement parsing, but still show the README and prompt the user to proceed.
.RE
+.P
+-w
+.RS
+When used in combination with the -f option, to force a slackbuild even if it would not constitute an update, this will cause sboupgrade to also rebuild all of that slackbuild's requirements that it can grok. Normally with -f, only the slackbuild(s) specified, and any requirements not already installed, will be rebuilt.
+.RE
.SH BUGS
.P
Requirement parsing is not foolproof; there are very likely corner cases where it does not function as expected. If any such cases are found, please report this to j@dawnrazor.net; patches are always welcome as well.