diff options
| -rw-r--r-- | man1/sbocheck.1 | 2 | ||||
| -rw-r--r-- | man1/sboconfig.1 | 6 | ||||
| -rw-r--r-- | man1/sbofind.1 | 4 | ||||
| -rw-r--r-- | man1/sboinstall.1 | 6 | ||||
| -rw-r--r-- | man1/sboupgrade.1 | 6 |
5 files changed, 12 insertions, 12 deletions
diff --git a/man1/sbocheck.1 b/man1/sbocheck.1 index 52c831e..e0f0e66 100644 --- a/man1/sbocheck.1 +++ b/man1/sbocheck.1 @@ -7,7 +7,7 @@ sbocheck - update a local slackbuilds.org tree and check for updates. sbocheck [-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 slackbuilds have updates, and reports what it finds. +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. .SH OPTIONS .P -v diff --git a/man1/sboconfig.1 b/man1/sboconfig.1 index 9a1343e..eea5eca 100644 --- a/man1/sboconfig.1 +++ b/man1/sboconfig.1 @@ -27,17 +27,17 @@ DISTCLEAN: If TRUE, then DO remove the source code after building the slackbuild .P -j (#|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. +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 -c (TRUE|FALSE) .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/slackbuild. 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). +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. 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 -p (/path|FALSE) .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. 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. +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. 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 (/path|/usr/sbo) diff --git a/man1/sbofind.1 b/man1/sbofind.1 index d8c12dd..e166c4f 100644 --- a/man1/sbofind.1 +++ b/man1/sbofind.1 @@ -1,13 +1,13 @@ .TH sbofind 1 "Prickle-Prickle, the 61st day of Discord in the YOLD 3178" "sbotools 0.3 fnord" dawnrazor.net .SH NAME .P -sbofind - search SlackBuilds for a given name +sbofind - search slackbuilds.org tree for a given name .SH SYNAPSES .P sbofind [-v] 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. +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. .SH OPTIONS .P -v diff --git a/man1/sboinstall.1 b/man1/sboinstall.1 index 8c6be06..1067a44 100644 --- a/man1/sboinstall.1 +++ b/man1/sboinstall.1 @@ -22,12 +22,12 @@ If TRUE, then DO remove the source code after building the slackbuild. By defaul .P -j (#|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. +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 -c (TRUE|FALSE) .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/slackbuild. 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. +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 .P -N @@ -42,7 +42,7 @@ Skip viewing of the README and the yes or no question which accompanies it. Anyt .P -i .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)). +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 -p diff --git a/man1/sboupgrade.1 b/man1/sboupgrade.1 index ae2af5a..a0ddb44 100644 --- a/man1/sboupgrade.1 +++ b/man1/sboupgrade.1 @@ -21,12 +21,12 @@ If TRUE, then DO remove the source code after building the slackbuild. By defaul .RE -j (#|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. +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 -c (TRUE|FALSE) .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/slackbuild. 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. +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 .P -f @@ -46,7 +46,7 @@ Skip viewing of the README and the yes or no question which accompanies it. Anyt .P -i .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)). +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 -v |