mirror of
https://github.com/sbopkg/sbopkg
synced 2025-01-18 10:26:27 +01:00
add html versions of both man pages and also output of 'sbopkg -h' to tools/ directory for sbopkg.org website usage
This commit is contained in:
chess.griffin
parent
d5a6a216e1
commit
5e39bc23d9
3 changed files with 772 additions and 0 deletions
395
tools/sbopkg-conf5.html
Normal file
395
tools/sbopkg-conf5.html
Normal file
|
|
@ -0,0 +1,395 @@
|
|||
Content-type: text/html
|
||||
|
||||
<HTML><HEAD><TITLE>Manpage of SBOPKG.CONF</TITLE>
|
||||
</HEAD><BODY>
|
||||
<H1>SBOPKG.CONF</H1>
|
||||
Section: (5)<BR>Updated: June 2009<BR><A HREF="#index">Index</A>
|
||||
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
||||
|
||||
<A NAME="lbAB"> </A>
|
||||
<H2>NAME</H2>
|
||||
|
||||
<B>sbopkg.conf</B>
|
||||
|
||||
- Configuration file for sbopkg
|
||||
<P>
|
||||
<A NAME="lbAC"> </A>
|
||||
<H2>DESCRIPTION</H2>
|
||||
|
||||
<P>
|
||||
The sbopkg.conf file contains configuration settings for
|
||||
<B>sbopkg</B>
|
||||
|
||||
(8), a tool for interacting with the SlackBuilds.org ("SBo")
|
||||
repository, a collection of third-party SlackBuild scripts to build
|
||||
Slackware packages. A sample file is provided at
|
||||
/etc/sbopkg/sbopkg.conf.new. Also, please see a note below about
|
||||
$ARCH.
|
||||
<P>
|
||||
The different configuration options are:
|
||||
<P>
|
||||
<DL COMPACT>
|
||||
<DT><B>REPO_NAME</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option allows the user to choose the repository to use.
|
||||
The default options are SBo, SB64 and local.
|
||||
The 'local' choice corresponds to a user-maintained repository whose
|
||||
structure must be the same as the one used by SlackBuilds.org. NOTE:
|
||||
all of the REPO_* variables are affected by the repository files
|
||||
maintained in /etc/sbopkg/repos.d. Please see the README-repos.d
|
||||
document in the sbopkg /doc directory.
|
||||
<P>
|
||||
The default value of REPO_NAME is:
|
||||
<BR>
|
||||
|
||||
REPO_NAME=${REPO_NAME:-SBo}.
|
||||
<P>
|
||||
<DT><B>REPO_BRANCH</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option allows the user to set the default active repository
|
||||
branch. The current options are 11.0, 12.0, 12.1, 12.2, and 13.0 for
|
||||
the SBo repository, master for the SB64 repositort and local for the
|
||||
local repository.
|
||||
<P>
|
||||
The default value of REPO_BRANCH is:
|
||||
<BR>
|
||||
|
||||
REPO_BRANCH=${REPO_BRANCH:-13.0}.
|
||||
<P>
|
||||
<DT><B>REPO_ROOT</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option allows the user to set the location of the local
|
||||
mirrors of the remote repositories. Currently, the size of a local copy of
|
||||
the SBo repository is less than 50MB.
|
||||
<P>
|
||||
The default value of REPO_ROOT is:
|
||||
<BR>
|
||||
|
||||
REPO_ROOT=${REPO_ROOT:-/var/lib/sbopkg}.
|
||||
<P>
|
||||
<DT><B>SRCDIR</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option contains the location of the cache directory where
|
||||
source downloads will be saved.
|
||||
<P>
|
||||
The default value of SRCDIR is:
|
||||
<BR>
|
||||
|
||||
SRCDIR=${SRCDIR:-/var/cache/sbopkg}.
|
||||
<P>
|
||||
<DT><B>SBOPKGTMP</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option sets the default directory where certain working
|
||||
files are saved on a temporary basis.
|
||||
<P>
|
||||
The default value of SBOPKGTMP is:
|
||||
<BR>
|
||||
|
||||
SBOPKGTMP=${SBOPKGTMP:-/tmp/sbopkg}.
|
||||
<P>
|
||||
<DT><B>TMP</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option sets the default directory where built packages should be stored.
|
||||
TMP must be exported as it is used by the SlackBuilds. Also note that the
|
||||
default value of TMP is the same as in the SBo SlackBuild scripts.
|
||||
<P>
|
||||
The default value of TMP is:
|
||||
<BR>
|
||||
|
||||
export TMP=${TMP:-/tmp/SBo}.
|
||||
<P>
|
||||
<DT><B>OUTPUT</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option sets the default directory where compiled packages are
|
||||
saved. OUTPUT must be exported as it is also used by the SBo
|
||||
SlackBuilds. Also note that the default value of OUTPUT is therefore
|
||||
the same as in the SBo SlackBuilds.
|
||||
<P>
|
||||
The default value of OUTPUT is:
|
||||
<BR>
|
||||
|
||||
export OUTPUT=${OUTPUT:-/tmp}.
|
||||
<P>
|
||||
<DT><B>QUEUEDIR</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option defines the directory under which saved queue files will
|
||||
be kept.
|
||||
<P>
|
||||
The default value of QUEUEDIR is:
|
||||
<BR>
|
||||
|
||||
QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}.
|
||||
<P>
|
||||
<DT><B>KEEPLOG</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option should be set to YES or NO. This option allows the user
|
||||
to choose whether to keep a permanent log of packages that are built
|
||||
with sbopkg in order to go back and review the build, and any errors,
|
||||
after exiting sbopkg. If set to YES, this permanent log is saved at
|
||||
$LOGDIR/sbopkg-build-log.
|
||||
<P>
|
||||
The default value of KEEPLOG is: YES.
|
||||
<P>
|
||||
<DT><B>LOGDIR</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option sets the location for the sbopkg permanent log if KEEPLOG
|
||||
is set to YES (see previous paragraph).
|
||||
<P>
|
||||
The default value of LOGDIR is:
|
||||
<BR>
|
||||
|
||||
LOGDIR=${LOGDIR:-/var/log/sbopkg}.
|
||||
<P>
|
||||
<DT><B>CLEANUP</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option should be set to YES or NO. When set to YES, the source
|
||||
files and the various residuals from the process of building a package
|
||||
are deleted right after the build.
|
||||
A side effect of setting CLEANUP to YES is that the TMP setting got
|
||||
from the environment or from the configuration files is ignored.
|
||||
<P>
|
||||
The default value of CLEANUP is: NO.
|
||||
<P>
|
||||
<DT><B>ALLOW_MULTI</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
When set to YES, this option allows the user to run multiple instances
|
||||
of sbopkg.
|
||||
<P>
|
||||
Please understand that this option is provided for convenience, but
|
||||
given the number of potential issues you can face when enabling this
|
||||
(and we aren't going to try to work around users doing silly things),
|
||||
you should consider working with ALLOW_MULTI=YES as an EXPERIMENTAL
|
||||
UNSUPPORTED feature. If you encounter problems, please try to make sure
|
||||
these aren't caused by yourself doing improper things.
|
||||
<P>
|
||||
For reference, these are some of the things you shouldn't do with this
|
||||
option enabled:
|
||||
<DL COMPACT><DT><DD>
|
||||
<DL COMPACT>
|
||||
<DT>[bu]<DD>
|
||||
run an ALLOW_MULTI=NO instance together with one or more having
|
||||
ALLOW_MULTI=YES
|
||||
<DT>[bu]<DD>
|
||||
sync a repository when another instance is using it
|
||||
<DT>[bu]<DD>
|
||||
change the branch of a git repository when another instance is using it
|
||||
(you can do this with rsync -- i.e. SlackBuild.org -- repos)
|
||||
<DT>[bu]<DD>
|
||||
simultaneously build or install the same package from different instances
|
||||
<DT>[bu]<DD>
|
||||
save a queue file while using it from another instance
|
||||
</DL>
|
||||
</DL>
|
||||
|
||||
<P>
|
||||
<DL COMPACT><DT><DD>
|
||||
There can be more unsafe situations we haven't thought about. Take care.
|
||||
</DL>
|
||||
|
||||
<P>
|
||||
<DT><B>DEBUG</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option should be set to 0, 1, or 2. DEBUG sets the default
|
||||
debugging level for the update list feature of sbopkg. When DEBUG is
|
||||
set to 0, then only potential updated (or downgraded) packages are listed.
|
||||
When DEBUG is set to 1, then potential updates plus packages not in the
|
||||
repo and packages that are newer than the repo are listed. When DEBUG is
|
||||
set to 2, all non-updated packages are also listed. Changing DEBUG to 1 or
|
||||
2 may be helpful if it appears the updatelist might be missing an update.
|
||||
<P>
|
||||
The default value of DEBUG is: 0.
|
||||
<P>
|
||||
<DT><B>RSYNCFLAGS</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
Rsync is used by sbopkg to mirror the SlackBuilds.org repository.
|
||||
This option allows the user to manually tweak the rsync flags
|
||||
(options) that are used by sbopkg. Users are cautioned against making
|
||||
any changes to the default values since new flags may or may not work.
|
||||
Note: the rsync command in sbopkg already uses the --archive,
|
||||
--delete, --no-owner, and --exclude flags, so there is no need to add
|
||||
them to the RSYNCFLAGS option. Changing these default options is not
|
||||
recommended.
|
||||
<P>
|
||||
The default value of RSYNCFLAGS is: "--timeout=10 --verbose".
|
||||
<P>
|
||||
<DT><B>WGETFLAGS</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
Wget is used by sbopkg to download the source files for package
|
||||
building. This option allows the user to manually tweak the wget
|
||||
flags (options) that are used by sbopkg. Users are cautioned against
|
||||
making any changes to the default values since new flags may or may
|
||||
not work. Note: the wget command in sbopkg already uses the -O flag,
|
||||
so there is no need to add that to the WGETFLAGS option. Changing
|
||||
these default options is not recommended.
|
||||
<P>
|
||||
The default value of WGETFLAGS is:
|
||||
<BR>
|
||||
|
||||
"--continue --progress-bar --timeout=15 --tries=5".
|
||||
<P>
|
||||
<DT><B>DIFF</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option allows the user to set which diff program to use when
|
||||
sbopkg displays differences between edited files.
|
||||
<P>
|
||||
The default value of DIFF is:
|
||||
<BR>
|
||||
|
||||
DIFF=${DIFF:-diff}.
|
||||
<P>
|
||||
<DT><B>DIFFOPTS</B>
|
||||
|
||||
<DD>
|
||||
<BR>
|
||||
|
||||
This option allows the user to set which options are used by the $DIFF
|
||||
program when sbopkg displays differences between edited files.
|
||||
<P>
|
||||
The default value of DIFFOPTS is:
|
||||
<P>
|
||||
DIFFOPTS=${DIFFOPTS:--u}
|
||||
<P>
|
||||
</DL>
|
||||
<A NAME="lbAD"> </A>
|
||||
<H2>OVERRIDING ENVIRONMENTAL VARIABLES</H2>
|
||||
|
||||
It is possible to set or override environmental variables and pass
|
||||
them to the SlackBuild scripts when they are built from within sbopkg.
|
||||
This is already demonstrated in the following line in the sbopkg.conf
|
||||
file:
|
||||
<P>
|
||||
export TMP=${TMP:-/tmp/SBo}
|
||||
<P>
|
||||
This sets $TMP to /tmp/SBo for building SBo packages within sbopkg (which is
|
||||
currently the default for SBo SlackBuilds already). Since this variable is
|
||||
exported, it could be changed for both sbopkg and for building SBo
|
||||
packages within sbopkg. For example, changing this line so it reads:
|
||||
<P>
|
||||
export TMP=${TMP:-/home/sbo/tmp}
|
||||
<P>
|
||||
would then set $TMP to /home/sbo/tmp for building SBo
|
||||
packages. OUTPUT can also be changed to save compiled packages in a
|
||||
location other than the default of /tmp.
|
||||
<P>
|
||||
Please note that if the CLEANUP variable is set to YES, the TMP setting
|
||||
is ignored.
|
||||
<P>
|
||||
You can also export variables in sbopkg.conf that are not used by
|
||||
sbopkg at all.
|
||||
<P>
|
||||
<A NAME="lbAE"> </A>
|
||||
<H2>ABOUT $ARCH</H2>
|
||||
|
||||
You may be wondering why $ARCH is not a configuration setting in the
|
||||
sbopkg.conf file. The reason is that it does not have to be. First, sbopkg
|
||||
does some checking (using 'uname -m') to determine what the system's
|
||||
architecture is. If the architecture is x86_64, then sbopkg automatically
|
||||
sets ARCH=x86_64. If the architecture is not x86_64, then sbopkg will inherit
|
||||
any $ARCH settings in the environment. This means, the user can add, for
|
||||
example, 'export ARCH=i686' in their .bashrc or similar file, or the user can
|
||||
also execute something in the root terminal like 'export ARCH=i686 && sbopkg'.
|
||||
The user can also manually add it to their sbopkg.conf file if they wish.
|
||||
Finally, if $ARCH is not set by the user and sbopkg does not detect an x86_64
|
||||
system, then $ARCH will default to whatever $ARCH is set to in the SlackBuild
|
||||
scripts.
|
||||
<P>
|
||||
<A NAME="lbAF"> </A>
|
||||
<H2>FILES</H2>
|
||||
|
||||
<B>/etc/sbopkg/sbopkg.conf</B>
|
||||
|
||||
- File to specify configuration options.
|
||||
<P>
|
||||
<B>/etc/sbopkg/renames.d/50-default</B>
|
||||
|
||||
- Default file that lists software in SBo repository that has been renamed.
|
||||
See the README-renames.d document in the sbopkg doc/ directory for more
|
||||
information.
|
||||
<P>
|
||||
<B>/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo}</B>
|
||||
|
||||
- Three default files for various types of sbopkg repositories. See the
|
||||
README-repos.d document in the sbopkg doc/ directory for more information.
|
||||
<P>
|
||||
<A NAME="lbAG"> </A>
|
||||
<H2>SEE ALSO</H2>
|
||||
|
||||
<B><A HREF="http://localhost/cgi-bin/man/man2html?8+sbopkg">sbopkg</A></B>(8)
|
||||
|
||||
<B>doc/README</B>
|
||||
|
||||
<B>doc/README-queuefiles</B>
|
||||
|
||||
<B>doc/README-renames.d</B>
|
||||
|
||||
<B>doc/README-repos.d</B>
|
||||
|
||||
<B>doc/queuefiles/*</B>
|
||||
|
||||
<P>
|
||||
|
||||
<HR>
|
||||
<A NAME="index"> </A><H2>Index</H2>
|
||||
<DL>
|
||||
<DT><A HREF="#lbAB">NAME</A><DD>
|
||||
<DT><A HREF="#lbAC">DESCRIPTION</A><DD>
|
||||
<DT><A HREF="#lbAD">OVERRIDING ENVIRONMENTAL VARIABLES</A><DD>
|
||||
<DT><A HREF="#lbAE">ABOUT $ARCH</A><DD>
|
||||
<DT><A HREF="#lbAF">FILES</A><DD>
|
||||
<DT><A HREF="#lbAG">SEE ALSO</A><DD>
|
||||
</DL>
|
||||
<HR>
|
||||
This document was created by
|
||||
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
|
||||
using the manual pages.<BR>
|
||||
Time: 03:24:28 GMT, February 01, 2010
|
||||
</BODY>
|
||||
</HTML>
|
||||
34
tools/sbopkg-help
Normal file
34
tools/sbopkg-help
Normal file
|
|
@ -0,0 +1,34 @@
|
|||
sbopkg 0.31.0
|
||||
Usage: sbopkg [OPTIONS] <packagename(s)>
|
||||
Options are:
|
||||
-b pkg/queue(s) Build the specified package(s). If one or more queuefiles
|
||||
are specified, build the packages they refer to.
|
||||
-c Check for updates to installed packages.
|
||||
-d localdir Location of local copy of the repositories.
|
||||
-e error_action Specify what sbopkg is supposed to do on build errors.
|
||||
Valid options are: ask (default), continue, stop.
|
||||
-f file Override default configuration file with specified file.
|
||||
-g package(s) General search for packages matching string.
|
||||
-h Display this help message.
|
||||
-i pkg/queue(s) Like '-b', but also install built packages.
|
||||
-k Skip installed packages when building.
|
||||
-l Display the repo's ChangeLog.txt and then quit.
|
||||
-o Display the obsolete source files and prompt for deletion.
|
||||
-p List installed repo's packages.
|
||||
-q Quiet some of the command-line output.
|
||||
-r Sync the remote repository with the local mirror and then
|
||||
quit.
|
||||
-R Preview the READMEs before starting the build process.
|
||||
-s package(s) Specific search by specific package and, if found,
|
||||
display package information.
|
||||
-u Check for an update to sbopkg.
|
||||
-v repo/branch Set the repository/branch (e.g. "-v SBo/13.0").
|
||||
If the repository name is not specified, sbopkg will first
|
||||
try with the default one. If no match is found, sbopkg will
|
||||
look for the first matching branch of any repository.
|
||||
The default valid choices are SBo/{11.0,12.0,12.1,12.2,13.0}
|
||||
for the SlackBuilds.org repository, SB64/master for the
|
||||
builds.Slamd64.com repository and local/local for the local
|
||||
repository).
|
||||
|
||||
Note: multiple arguments to -b, -g, -i, and -s must be quoted ("pkg1 pkg2")
|
||||
343
tools/sbopkg8.html
Normal file
343
tools/sbopkg8.html
Normal file
|
|
@ -0,0 +1,343 @@
|
|||
Content-type: text/html
|
||||
|
||||
<HTML><HEAD><TITLE>Manpage of SBOPKG</TITLE>
|
||||
</HEAD><BODY>
|
||||
<H1>SBOPKG</H1>
|
||||
Section: (8)<BR>Updated: August 2009<BR><A HREF="#index">Index</A>
|
||||
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
|
||||
|
||||
<A NAME="lbAB"> </A>
|
||||
<H2>NAME</H2>
|
||||
|
||||
<B>sbopkg</B>
|
||||
|
||||
- The SlackBuilds.org Package Browser
|
||||
<P>
|
||||
<A NAME="lbAC"> </A>
|
||||
<H2>SYNOPSIS</H2>
|
||||
|
||||
<B>sbopkg</B>
|
||||
|
||||
<B>[options]</B>
|
||||
|
||||
<P>
|
||||
<A NAME="lbAD"> </A>
|
||||
<H2>DESCRIPTION</H2>
|
||||
|
||||
Sbopkg is a command-line and dialog-based tool to interact with the
|
||||
SlackBuilds.org ("SBo") repository, a collection of third-party
|
||||
SlackBuild scripts to build Slackware packages.
|
||||
<P>
|
||||
<A NAME="lbAE"> </A>
|
||||
<H2>INSTRUCTIONS</H2>
|
||||
|
||||
Sbopkg usage assumes an understanding of SlackBuild scripts,
|
||||
generally, and the third-party repository SlackBuilds.org,
|
||||
specifically. A thorough reading of <A HREF="http://www.slackbuilds.org/howto/">http://www.slackbuilds.org/howto/</A>
|
||||
and the pages at <A HREF="http://www.slackwiki.org">http://www.slackwiki.org</A> about SlackBuild scripts is
|
||||
strongly advised.
|
||||
<P>
|
||||
Before sbopkg can be used, a configuration file must be created at
|
||||
/etc/sbopkg/sbopkg.conf. A sample file is provided at
|
||||
/etc/sbopkg/sbopkg.conf.new. See
|
||||
<B>sbopkg.conf</B>
|
||||
|
||||
(5) for more information about the configuration file.
|
||||
<P>
|
||||
Sbopkg can be run from the command line by simply invoking "sbopkg."
|
||||
Doing so will launch the dialog-based interface, and the menus
|
||||
provided should be fairly self-explanatory. The main menu allows the
|
||||
user to rsync with the SlackBuilds.org repository (currently, the size
|
||||
of a local copy of the SBo repository is less than 50MB), view the
|
||||
SlackBuilds.org Changelog, check for potential updates to SBo
|
||||
packages, display the contents of the local cache directory where
|
||||
source tarballs are saved, display the permanent build log, and browse
|
||||
or search the local copy of the SBo repository. Once the browse
|
||||
function is chosen, the user can select the category of software to
|
||||
view. After choosing a category, the user can then view the various
|
||||
software packages available in that category within the local SBo
|
||||
repository. Selecting a package will display another menu allowing
|
||||
the user to view the package's README, SlackBuild, .info, or
|
||||
slack-desc files. The user can also edit the .info file and
|
||||
SlackBuild and the edited files will remain after doing an rsync.
|
||||
Additionally, the user can
|
||||
choose to build a package as well using either the original SlackBuild
|
||||
or the locally-edited one, if present. If using the dialog interface,
|
||||
and if sbopkg finds a built package for a particular piece of software
|
||||
in the OUTPUT directory, then sbopkg will automatically add a new menu
|
||||
entry allowing the user to install the package if he so choosed.
|
||||
Alternatively, the user can choose to automatically build or build and
|
||||
install individual packages or several packages in a build queue.
|
||||
Finally, if KEEPLOG is set to YES in the sbopkg.conf file then a
|
||||
permanent log of the build process is saved in /tmp/sbopkg-build-log.
|
||||
<P>
|
||||
Alternatively, sbopkg can be run from the command line without using
|
||||
the dialog interface. Executing "sbopkg -h" will display a list of
|
||||
options available from the command line.
|
||||
<P>
|
||||
Sbopkg also has the capability of loading, saving, and using
|
||||
user-created queuefiles. These queuefiles are simple text files with
|
||||
one application name per line. By default, when a queuefile is loaded
|
||||
in the dialog interface, the application is selected, or "ON." This
|
||||
can be changed by inserting a "-" in front of the application name in
|
||||
the queuefile. Also, queuefiles can reference other queuefiles when
|
||||
the first character is a "@". See the readme-queuefiles document in
|
||||
the doc/ directory for more information.
|
||||
<P>
|
||||
Certain features of sbopkg rely on outside binaries, such as a pager
|
||||
to view the text files when sbopkg is run from the comamnd line, and
|
||||
an editor to edit the .info or SlackBuild files. The pager function
|
||||
will look to the environmental variable $PAGER and if that variable is
|
||||
not defined then it will default to 'more.' Similarly, the edit
|
||||
function found when sbopkg is used with the dialog interface will look
|
||||
to $EDITOR and will default to 'vi' if no $EDITOR has been defined.
|
||||
If the user wants sbopkg to use another $EDITOR, such as nano, then
|
||||
adding the requisite information in ~/.bashrc, /etc/profile, or other
|
||||
similar configuration file to export $EDITOR will suffice.
|
||||
<P>
|
||||
<A NAME="lbAF"> </A>
|
||||
<H2>OPTIONS</H2>
|
||||
|
||||
<DL COMPACT>
|
||||
<DT><B>-b PACKAGE(s)/QUEUE(s)</B>
|
||||
|
||||
<DD>
|
||||
Search for and build PACKAGE(s) from the local SBo repository. If more
|
||||
than one package is specified, they must be in quotes. For example:
|
||||
<P>
|
||||
#sbopkg -b "foo bar"
|
||||
<P>
|
||||
will build foo and then bar.
|
||||
Queuefile names can also be specified. In that case, all the packages
|
||||
specified in the queuefile will be built. In the unfortunate case a
|
||||
token matches both a queuefile name and a package name (i.e. the user
|
||||
named a queuefile with the name of a package), sbopkg will ask the user
|
||||
which one should be used. The tokens (package names or queuefiles)
|
||||
are processed in the order they are specified on the command line, and
|
||||
the build order specified in the queuefiles is retained. If a package
|
||||
is specified more than once, it gets queued only the first time it is
|
||||
encountered.
|
||||
<P>
|
||||
<DT><B>-c</B>
|
||||
|
||||
<DD>
|
||||
Display list of installed SBo packages and potential updates.
|
||||
<P>
|
||||
<DT><B>-d DIRECTORY</B>
|
||||
|
||||
<DD>
|
||||
Manually specify the full path to the DIRECTORY containing the
|
||||
local SBo repository.
|
||||
<P>
|
||||
<DT><B>-e ask|continue|stop</B>
|
||||
|
||||
<DD>
|
||||
Specify what sbopkg should do when it encounters an error while building a
|
||||
package. Valid options are:
|
||||
<P>
|
||||
<B>ask</B>
|
||||
|
||||
: This is the default behavior, asking the user what to do;
|
||||
<P>
|
||||
<B>continue</B>
|
||||
|
||||
: Ignore the error and continue processing (act as if the user
|
||||
answered "Yes" to all questions);
|
||||
<P>
|
||||
<B>stop</B>
|
||||
|
||||
: Stop the processing (act as if the user answered "No" to all
|
||||
questions).
|
||||
<P>
|
||||
<DT><B>-f</B>
|
||||
|
||||
<DD>
|
||||
Override the default configuration file, which is located by
|
||||
default at /etc/sbopkg/sbopkg.conf, with another configuration
|
||||
file.
|
||||
<P>
|
||||
<DT><B>-g PACKAGE(s)</B>
|
||||
|
||||
<DD>
|
||||
General search for PACKAGE(s) by glob. For example:
|
||||
<P>
|
||||
#sbopkg -g nv
|
||||
<P>
|
||||
will return a list of matches, such as the nvidia packages,
|
||||
konversation, and other packages with 'nv' in their name. If more
|
||||
than one glob is specified, they must be in quotes.
|
||||
<P>
|
||||
<DT><B>-h</B>
|
||||
|
||||
<DD>
|
||||
Display the help.
|
||||
<P>
|
||||
<DT><B>-i PACKAGE(s)</B>
|
||||
|
||||
<DD>
|
||||
Search for and build and then install PACKAGE(s) from the local SBo
|
||||
repository. If more than one package is specified, they must be in
|
||||
quotes, and the packages will be built and then installed in the
|
||||
listed order. For example:
|
||||
<P>
|
||||
#sbopkg -i "foo bar"
|
||||
<P>
|
||||
will build and install foo and then build and install bar. By
|
||||
carefully considering the order of the packages listed, the user may
|
||||
be able to build and install dependencies in the right order before
|
||||
the final application is built and installed. Of course, given the
|
||||
nature of dependencies, this may not always be possible and so
|
||||
building dependencies like this is not really a supported feature.
|
||||
Still, when when it works, it can be helpful.
|
||||
<P>
|
||||
Queuefile names are supported, too. See the explanation for the '-b'
|
||||
command for details.
|
||||
<P>
|
||||
<DT><B>-k</B>
|
||||
|
||||
<DD>
|
||||
When used together with -b or -i, this option tells sbopkg to skip
|
||||
(i.e. don't build) any package it finds to be already installed.
|
||||
<P>
|
||||
Please note that only a name comparison is performed, so when this
|
||||
option is specified sbopkg will also omit the build of different
|
||||
versions of installed packages.
|
||||
<P>
|
||||
<DT><B>-l</B>
|
||||
|
||||
<DD>
|
||||
Display the SBo ChangeLog.txt and quit.
|
||||
<P>
|
||||
<DT><B>-o</B>
|
||||
|
||||
<DD>
|
||||
List the currently installed cached source files which are deemed as
|
||||
obsolete, and optionally delete them.
|
||||
<P>
|
||||
Source files are obsolete when no SBo script references it any more,
|
||||
which is something that can happen after rsync-ing the local
|
||||
repository.
|
||||
<P>
|
||||
Please note that only the currently active repository is
|
||||
used to identify the obsoleted sources, so if you build packages with
|
||||
different repositories (e.g. for different Slackware versions) the
|
||||
source files only used in the "other" repository will be listed.
|
||||
<P>
|
||||
<DT><B>-p</B>
|
||||
|
||||
<DD>
|
||||
List installed SlackBuilds.org packages.
|
||||
<P>
|
||||
<DT><B>-q</B>
|
||||
|
||||
<DD>
|
||||
Enable the "quiet mode." When this flag is specified, the output of
|
||||
some of the command-line options is minimized.
|
||||
<P>
|
||||
<DT><B>-r</B>
|
||||
|
||||
<DD>
|
||||
Rsync the local repository with SlackBuilds.org and quit.
|
||||
<P>
|
||||
<DT><B>-R</B>
|
||||
|
||||
<DD>
|
||||
Show all the README files of the queued packages before starting the build.
|
||||
This is useful when you want to make a final check.
|
||||
<P>
|
||||
<DT><B>-s PACKAGE(s)</B>
|
||||
|
||||
<DD>
|
||||
Specific search for PACKAGE(s) by PACKAGE name and, if found, display
|
||||
the README, SlackBuild, .info, and slack-desc files in that order
|
||||
using $PAGER, which defaults to 'more' as described above. If more
|
||||
than one package is specified, they must be in quotes. For example:
|
||||
<P>
|
||||
#sbopkg -s "foo bar"
|
||||
<P>
|
||||
will search for foo and then bar.
|
||||
<P>
|
||||
<DT><B>-u</B>
|
||||
|
||||
<DD>
|
||||
Check for an update to sbopkg itself and then quit.
|
||||
<P>
|
||||
<DT><B>-v VERSION</B>
|
||||
|
||||
<DD>
|
||||
Set the repository and branch to use.
|
||||
<P>
|
||||
The currently supported repositories are SBo, SB64 and local. Inside
|
||||
these, the supported branches are 11.0, 12.0, 12.1, 12.2, and 13.0 for
|
||||
SBo, master for SB64 (Slamd64Builds repository) and local for local.
|
||||
See the
|
||||
<B>sbopkg.conf (5)</B>
|
||||
|
||||
man page for more information about the 'local' repository.
|
||||
<P>
|
||||
The VERSION format is repository/branch (e.g. SBo/13.0). If the repository is
|
||||
omitted, sbopkg will first look for the specified branch in the default
|
||||
repository. If that attempt fails, sbopkg will look for the first matching
|
||||
branch in any repository.
|
||||
<P>
|
||||
</DL>
|
||||
<A NAME="lbAG"> </A>
|
||||
<H2>FILES</H2>
|
||||
|
||||
<B>/etc/sbopkg/sbopkg.conf</B>
|
||||
|
||||
- File to specify configuration options.
|
||||
<P>
|
||||
<B>/etc/sbopkg/renames.d/50-default</B>
|
||||
|
||||
- Default file that lists software in SBo repository that has been renamed.
|
||||
See the README-renames.d document in the sbopkg doc/ directory for more
|
||||
information.
|
||||
<P>
|
||||
<B>/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo}</B>
|
||||
|
||||
- Three default files for various types of sbopkg repositories. See the
|
||||
README-repos.d document in the sbopkg doc/ directory for more information.
|
||||
<P>
|
||||
<A NAME="lbAH"> </A>
|
||||
<H2>SEE ALSO</H2>
|
||||
|
||||
<B><A HREF="http://localhost/cgi-bin/man/man2html?5+sbopkg.conf">sbopkg.conf</A></B>(5)
|
||||
|
||||
<B>doc/README</B>
|
||||
|
||||
<B>doc/README-queuefiles</B>
|
||||
|
||||
<B>doc/README-renames.d</B>
|
||||
|
||||
<B>doc/README-repos.d</B>
|
||||
|
||||
<B>doc/queuefiles/*</B>
|
||||
|
||||
<P>
|
||||
<A NAME="lbAI"> </A>
|
||||
<H2>AUTHOR</H2>
|
||||
|
||||
Chess Griffin
|
||||
<<A HREF="mailto:chess@chessgriffin.com">chess@chessgriffin.com</A>>
|
||||
<P>
|
||||
|
||||
<HR>
|
||||
<A NAME="index"> </A><H2>Index</H2>
|
||||
<DL>
|
||||
<DT><A HREF="#lbAB">NAME</A><DD>
|
||||
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
|
||||
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
|
||||
<DT><A HREF="#lbAE">INSTRUCTIONS</A><DD>
|
||||
<DT><A HREF="#lbAF">OPTIONS</A><DD>
|
||||
<DT><A HREF="#lbAG">FILES</A><DD>
|
||||
<DT><A HREF="#lbAH">SEE ALSO</A><DD>
|
||||
<DT><A HREF="#lbAI">AUTHOR</A><DD>
|
||||
</DL>
|
||||
<HR>
|
||||
This document was created by
|
||||
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
|
||||
using the manual pages.<BR>
|
||||
Time: 03:22:01 GMT, February 01, 2010
|
||||
</BODY>
|
||||
</HTML>
|
||||
Loading…
Reference in a new issue