consistency and cleanup fixes, updated ddate and version

8 files changed, 21 insertions, 21 deletions

diff --git a/man1/sbocheck.1 b/man1/sbocheck.1
index d2ccf6c..35cf529 100644
--- a/man1/sbocheck.1
+++ b/man1/sbocheck.1
@@ -1,4 +1,4 @@
-.TH sbocheck 1 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sbocheck 1 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 fnord" dawnrazor.net
 .SH NAME
 .P
 sbocheck - update a local slackbuilds.org tree and check for updates.
diff --git a/man1/sboclean.1 b/man1/sboclean.1
index 5b64bd3..aa2f1d5 100644
--- a/man1/sboclean.1
+++ b/man1/sboclean.1
@@ -1,10 +1,10 @@
-.TH sboclean 1 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sboclean 1 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 fnord" dawnrazor.net
 .SH NAME
 .P
 sboclean - clean files left around by sbotools.
 .SH SYNAPSES
 .P
-sboclean [-hvdwi]
+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. Note that if not run with the -i flag, sboclean will remove anything in the distfiles or /tmp/SBo folders with extreme prejudice. One of either -d or -w must be specified for this script to do anything.
diff --git a/man1/sboconfig.1 b/man1/sboconfig.1
index ae502bb..9ed8bfd 100644
--- a/man1/sboconfig.1
+++ b/man1/sboconfig.1
@@ -1,10 +1,10 @@
-.TH sboconfig 1 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sboconfig 1 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 fnord" dawnrazor.net
 .SH NAME
 .P
 sboconfig - set sbotools configuration options.
 .SH SYNAPSES
 .P
-sboconfig [-h] [-l] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-p /path|FALSE] [-s /path|/usr/sbo] [-v]
+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.
diff --git a/man1/sbofind.1 b/man1/sbofind.1
index 2decf2b..6b4d8e6 100644
--- a/man1/sbofind.1
+++ b/man1/sbofind.1
@@ -1,10 +1,10 @@
-.TH sbofind 1 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sbofind 1 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 fnord" dawnrazor.net
 .SH NAME
 .P
 sbofind - search slackbuilds.org tree for a given name
 .SH SYNAPSES
 .P
-sbofind [-hvir] search_term
+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. For a more general search, the slackbuilds.org site should be consulted, where tags also exist and are included in the searched fields.
diff --git a/man1/sboinstall.1 b/man1/sboinstall.1
index 8eb73fa..d269f20 100644
--- a/man1/sboinstall.1
+++ b/man1/sboinstall.1
@@ -1,4 +1,4 @@
-.TH sboinstall 1 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sboinstall 1 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 fnord" dawnrazor.net
 .SH NAME
 .P
 sboinstall - install slackbuilds
@@ -7,7 +7,7 @@ sboinstall - install slackbuilds
 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.
+sboinstall is equivalent to sboupgrade -N, but is faster since it only installs new slackbuilds, so is preferred for installs. 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. This is recursive, so that ordering happens correctly. 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.
 .SH OPTIONS
 .P
 -h|--help
@@ -20,7 +20,7 @@ Show help information.
 Show version information.
 .RE
 .P
--c|--noclean (TRUE|FALSE)
+-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. 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
@@ -47,19 +47,19 @@ Create a -compat32 package instead of a normal x86_64 package on multilib x86_64
 .P
 -r|--nointeractive
 .RS
-Skip viewing of the README and the yes or no question which accompanies it. Anytime sboupgrade or 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. If multiple slackbuilds are specified, this option bypasses them all.
+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. If multiple slackbuilds are specified, this option bypasses them all.
 .RE
 .P
 -R|--norequirements
 .RS
-This option causes sboupgrade to skip requirement parsing, but still show the README and prompt the user to proceed.
+This option causes sboinstall to skip requirement parsing, but still show the README and prompt the user to proceed.
 .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.
+Requirement parsing is not foolproof; there are corner cases where it does not function as expected.
 .SH SEE ALSO
 .P
-sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sbosnap(1), sbotools.conf(5)
+sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sbosnap(1), sboupgrade(1), sbotools.conf(5)
 .SH AUTHOR
 .P
 Jacob Pipkin <j@dawnrazor.net>
diff --git a/man1/sbosnap.1 b/man1/sbosnap.1
index 2f7bafd..f88a134 100644
--- a/man1/sbosnap.1
+++ b/man1/sbosnap.1
@@ -1,4 +1,4 @@
-.TH sbosnap 1 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sbosnap 1 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 fnord" dawnrazor.net
 .SH NAME
 .P
 sbosnap - slackbuilds.org tree fetch and update command.
diff --git a/man1/sboupgrade.1 b/man1/sboupgrade.1
index 583e06f..5db83dc 100644
--- a/man1/sboupgrade.1
+++ b/man1/sboupgrade.1
@@ -1,13 +1,13 @@
-.TH sboupgrade 1 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sboupgrade 1 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 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] [-z] sbo_name (sbo_name)
+sboupgrade [-h|-v] [-c TRUE|FALSE] [-d TRUE|FALSE] [-j #|FALSE] [-fNrRiz] 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 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.
+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. This is recursive, so that ordering happens correctly. 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
 -h|--help
@@ -66,10 +66,10 @@ When used in combination with the -f option, to force an update even if it would
 .RE
 .SH BUGS
 .P
-Requirement parsing is not foolproof; there are 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.
+Requirement parsing is not foolproof; there are corner cases where it does not function as expected.
 .SH SEE ALSO
 .P
-sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sbosnap(1), sbotools.conf(5)
+sbocheck(1), sboclean(1), sboconfig(1), sbofind(1), sboinstall(1), sbosnap(1), sbotools.conf(5)
 .SH AUTHOR
 .P
 Jacob Pipkin <j@dawnrazor.net>
diff --git a/man5/sbotools.conf.5 b/man5/sbotools.conf.5
index da55800..f384835 100644
--- a/man5/sbotools.conf.5
+++ b/man5/sbotools.conf.5
@@ -1,4 +1,4 @@
-.TH sbotools.conf 5 "Sweetmorn, Bureaucracy 57, 3178 YOLD" "sbotools 0.9 fnord" dawnrazor.net
+.TH sbotools.conf 5 "Boomtime, Bureaucracy 58, 3178 YOLD" "sbotools 0.10 fnord" dawnrazor.net
 .SH NAME
 .P
 sbotools.conf - configuration file for sbotools commands.