commit 744d5682936a04179344e79a16f82014d77f457c
parent ca8c68a29f06db05e038f6a21895468f5298d884
Author: Jacob Pipkin <j@dawnrazor.net>
Date: Thu, 4 Oct 2012 05:07:31 -0500
man pages consistency and cleanup fixes
Diffstat:
5 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/man1/sbocheck.1 b/man1/sbocheck.1
@@ -4,7 +4,7 @@
sbocheck - update a local slackbuilds.org tree and check for updates.
.SH SYNAPSES
.P
-sbocheck [-v]
+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.
diff --git a/man1/sbofind.1 b/man1/sbofind.1
@@ -22,7 +22,7 @@ Show version information.
.P
-i|--info
.RS
-Show the contents of a the .info file for each slackbuild found.
+Show the contents of the .info file for each slackbuild found.
.RE
.P
-r|--readme
diff --git a/man1/sboinstall.1 b/man1/sboinstall.1
@@ -4,7 +4,7 @@
sboinstall - install slackbuilds
.SH SYNAPSES
.P
-sboinstall [-h] [-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-N] [-r] [-R] [-i] [-p] sbo_name (sbo_name)
+sboinstall [-h|-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-NrRip] sbo_name (sbo_name)
.SH DESCRIPTION
.P
sboinstall is equivalent to sboupgrade -N, but is faster, so is preferred if only installing one or more new packages. If the -r flag is NOT specified, sboinstall will attempt to grok a list of requirements in the README for a given 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. Note that this method is FAR from foolproof, which is why this does not happen if the README is bypassed. sboinstall 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, sboinstall will offer the opportunity to set options.
diff --git a/man1/sbosnap.1 b/man1/sbosnap.1
@@ -4,7 +4,7 @@
sbosnap - slackbuilds.org tree fetch and update command.
.SH SYNAPSES
.P
-sbosnap [-v] (fetch|update)
+sbosnap [-h|-v] (fetch|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.
diff --git a/man1/sboupgrade.1 b/man1/sboupgrade.1
@@ -39,6 +39,7 @@ Force an upgrade, even if the installed version is equal to or less than the sla
.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 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.
@@ -61,7 +62,7 @@ This option causes sboupgrade to skip requirement parsing, but still show the RE
.P
-z|--force-reqs
.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.
+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 that it can grok. 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
.SH BUGS
.P
