diff options
| -rw-r--r-- | man1/sboinstall.1 | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/man1/sboinstall.1 b/man1/sboinstall.1 index 6da268c..8963151 100644 --- a/man1/sboinstall.1 +++ b/man1/sboinstall.1 @@ -4,7 +4,7 @@ sboinstall - install SBos .SH SYNAPSES .P -sboinstall [-h] [-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-N] [-r] [-i] sbo_name (sbo_name) +sboinstall [-h] [-v] [-d TRUE|FALSE] [-j #|FALSE] [-c TRUE|FALSE] [-N] [-r] [-i] [-p] 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. @@ -45,6 +45,11 @@ Skip viewing of the README and the yes or no question which accompanies it. Anyt 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 +.RS +Create a -compat32 package instead of a normal x86_64 package on multilib x86_64 systems. This requires /usr/sbin/convertpkg-compat32; this can at least be obtained from AlienBob's compat32-tools package - see http://alien.slackbook.org/blog/. Note that this may or may not be foolproof, and is not supported by anyone; not me, not AlienBob, not Slackware, etc. I recommend using this with the -i option so that the created package can be inspected prior to installation. If you find that a particular SBo needs additional help to be created as -compat32 package, contact me at j@dawnrazor.net. +.RE +.P -v .RS Show sbotools version information. |