commit c7af49421065f707e22db085b59191be74a99ad1
parent 338ae6ada059b1cd53ac6f5c9280c0ea46366e8a
Author: Jacob Pipkin <d4wnr4z0r@yahoo.com>
Date: Mon, 28 May 2012 13:20:19 -0500
corrected wording regarding requirement parsing
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man1/sboupgrade.1 b/man1/sboupgrade.1
@@ -7,7 +7,7 @@ sboupgrade - install or upgrade slackbuilds
sboupgrade [-h] [-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-f] [-N] [-r] [-i] sbo_name (sbo_name)
.SH DESCRIPTION
.P
-sboupgrade is used to upgrade packages installed from slackbuilds. For new package installations, 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 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.
.SH OPTIONS
.P
-h
