mirrors/sbopkg
2
0
Fork 0
mirror of https://github.com/sbopkg/sbopkg synced 2024-11-09 19:50:25 +03:00
Code Issues Packages Projects Releases Wiki Activity

tag and release 0.34.0

Browse Source
This commit is contained in:
slakmagik 2010-11-12 04:07:45 +00:00
parent 23fc2049ca
commit dac7bd21c9
10 changed files with 1351 additions and 606 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/usr/doc/ChangeLog.txt
View File

@ -1,5 +1,5 @@
Thu May 27 18:13:59 UTC 2010 Fri Nov 12 03:37:16 UTC 2010
Sbopkg X.XX.X released. This version contains the following fixes and Sbopkg 0.34.0 released. This version contains the following fixes and
enhancements: enhancements:
* Revised man pages - these are very different and now document a couple of * Revised man pages - these are very different and now document a couple of

84
tools/ChangeLog-latest.txt
View File

@ -1,41 +1,49 @@
Thu May 27 18:13:59 UTC 2010 Fri Nov 12 03:37:16 UTC 2010
Sbopkg 0.33.1 released. This version contains the following fixes and Sbopkg 0.34.0 released. This version contains the following fixes and
enhancements: enhancements:
* The ARCH assignment was modified to accord with the latest SBo SlackBuild * Revised man pages - these are very different and now document a couple of
template. previously undocumented things and are worth a (re-)read. Thanks to
* Tweaked widgets in select_repository() (no or less scrolling) and Marie-Claude Collilieux for the French translations of these.
load_user_queue() (better button) and modified check_gpg() to not disrupt * The HACKING file now includes a man page style guide in addition to the
the dialog interface with gpg output coding style guide.
* Revised the KNOWN_ISSUES file and other documentation * The LOGDIR variable has been removed from sbopkg.conf - DIR can be
+--------------------------+ specified in LOGFILE.
Mon May 24 20:53:43 UTC 2010 * The DEBUG variable has been renamed to DEBUG_UPDATES in sbopkg.conf.
Sbopkg 0.33.0 released. This version contains the following fixes and * The default timeout values in {WGET,RSYNC}FLAGS have been raised from
enhancements: 10/15 to 30 in sbopkg.conf.
* All parameters in sbopkg.conf now use default values only if the variable
* Addressed an apparent bash 4.1 bug that causes the 'obsolete sources' hasn't been previously set (meaning they can all be overridden by passing
function to break. variables on the command line).
* Addressed issue 44 where hitting ^C during the download of part of a queue * sbopkg.conf has been reordered - this may make any merging that may be
and restarting the queue could result in a download failure. Thanks to needed more interesting this time but hopefully it's worth it.
slava18 for the report. * The directory initialization process has been changed - at first run or
* Changed the menu order of the "Build options" dialog to default to using otherwise when encountering missing directories, the user will now be
"Saved" options rather than "None". presented with a single list of them and a (C)reate/(A)bort prompt.
* Fixed issue 45 where packages with '+' in the name were not properly * The command line user interface has been overhauled in terms of more
detected in some cases. Thanks to skalkoto for the report. consistent validated command line messages and prompts.
* Added a help item to the main menu of the dialog interface with pointers * Fix an ARCH display issue in the updates screen; thanks to alkos333, Marc
to documentation and other resources. Payne, and David Spencer for confirming the issue and thanks to David
* Added an option to print the version of sbopkg. We try not to change the Spencer for testing the fix.
meaning of flags but note that this does change what was the '-v' flag to * Fixed bugs with dzen2 and *zarafa* not downloading/building properly. Note
'-V' and now uses '-v' for its customary 'version' purpose. Note that the that, while the changes fix these issues and should make it easier to
new -V flag now accepts a '?' argument (sbopkg -V ?) which will display handle similar problems in the future, this change may introduce
the list of valid repositories. regressions. If a download or build fails due to a downloaded tarball
* Tweak the logic re determining ARCH and modify some ARCH-related looking something like 'blah?actual_tarball.tar.gz' or the like, please
evals and conditionals in check_for_updates and info_item. report it to us.
* Fixed a bug which could result in some sources being missed when checking * Fixed bugs with the '-s' option where only the first of multiple
for obsolete sources. arguments would be returned and where the command line select menu was
* Added a command line option '-P' to access the 'remove uninstalled broken. Also where it and the -g flag might inadvertently expand globs
packages' function which had previously only been accessible from the wrongly.
dialog interface. * It's now possible to specify the b,g,i,s flags multiple times. Previously
* Miscellaneous tweaks in preparation for release and to bring in line with multiple arguments to these flags had to be quoted (-b "foo bar") but now
Slackware 13.1. they can be given as '-b foo -b bar'. The original style is still
supported.
* With the new style of passing multiple arguments, it is now possible to
specify app-specific options on the command line. These take the form of,
e.g., '-i app1:opt1="foo bar":opt2=baz app2:opt=mu'. If that's cryptic,
see the manual for details.
* Users now have the option of interactively retrying a failed https
download, invoking wget with '--no-check-certificate', as this can be
caused by 'self-signed certificates' and the like.
+--------------------------+ +--------------------------+

2
tools/current-download
View File

@ -1 +1 @@
http://sbopkg.googlecode.com/files/sbopkg-0.33.2-noarch-1_cng.tgz http://sbopkg.googlecode.com/files/sbopkg-0.34.0-noarch-1_cng.tgz

2
tools/current-package
View File

@ -1 +1 @@
sbopkg-0.33.2-noarch-1_cng.tgz sbopkg-0.34.0-noarch-1_cng.tgz

2
tools/current-source
View File

@ -1 +1 @@
sbopkg-0.33.2.tar.gz sbopkg-0.34.0.tar.gz

2
tools/current-version
View File

@ -1 +1 @@
0.33.2 0.34.0

1009
tools/sbopkg-conf5.html
View File

File diff suppressed because it is too large Load Diff

8
tools/sbopkg-help
View File

@ -1,4 +1,4 @@
sbopkg 0.33.1 sbopkg 0.34.0
Usage: sbopkg [OPTIONS] <packagename(s)> Usage: sbopkg [OPTIONS] <packagename(s)>
Options are: Options are:
-b pkg/queue(s) Build the specified package(s). If one or more queuefiles -b pkg/queue(s) Build the specified package(s). If one or more queuefiles
@ -29,4 +29,8 @@ Options are:
starting with the default repo. For a list of valid repos, starting with the default repo. For a list of valid repos,
issue '-V ?' issue '-V ?'
Note: multiple arguments to -b, -g, -i, and -s must be quoted ("pkg1 pkg2") Note: multiple arguments to -b, -g, -i, and -s must be quoted ("pkg1 pkg2") or
can be specified multiple times (-i foo -i bar). If using the latter syntax,
build options may also be passed on the command line on a per app basis using
the -b or -i flags in colon-separated groups (where whitespace must also be
quoted). For example, '-i app:opt1="arg1 arg2":opt2=arg1 app2'

2
tools/sbopkg.SlackBuild
View File

@ -8,7 +8,7 @@
# SlackBuilds.org template. # SlackBuilds.org template.
PRGNAM=sbopkg PRGNAM=sbopkg
VERSION=${VERSION:-0.33.1} VERSION=${VERSION:-0.34.0}
ARCH=${ARCH:-noarch} ARCH=${ARCH:-noarch}
BUILD=${BUILD:-1} BUILD=${BUILD:-1}
TAG=${TAG:-_cng} TAG=${TAG:-_cng}

842
tools/sbopkg8.html
View File

@ -3,359 +3,723 @@ Content-type: text/html
<HTML><HEAD><TITLE>Manpage of SBOPKG</TITLE> <HTML><HEAD><TITLE>Manpage of SBOPKG</TITLE>
</HEAD><BODY> </HEAD><BODY>
<H1>SBOPKG</H1> <H1>SBOPKG</H1>
Section: (8)<BR>Updated: May 2010<BR><A HREF="#index">Index</A> Section: (8)<BR>Updated: November 2010<BR><A HREF="#index">Index</A>
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR> <A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
<A NAME="lbAB">&nbsp;</A> <A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2> <H2>NAME</H2>
<B>sbopkg</B> sbopkg - the SlackBuilds.org package browser
&nbsp;- The SlackBuilds.org Package Browser
<P>
<A NAME="lbAC">&nbsp;</A> <A NAME="lbAC">&nbsp;</A>
<H2>SYNOPSIS</H2> <H2>SYNOPSIS</H2>
<B>sbopkg</B> <B>sbopkg</B>
<B>[options]</B> [<I>options</I>]
<P>
<A NAME="lbAD">&nbsp;</A> <A NAME="lbAD">&nbsp;</A>
<H2>DESCRIPTION</H2> <H2>DESCRIPTION</H2>
Sbopkg is a command-line and dialog-based tool to interact with the <B>Sbopkg</B>
SlackBuilds.org (&quot;SBo&quot;) repository, a collection of third-party
SlackBuild scripts to build Slackware packages. is a command-line and
<P> <B>dialog</B>-based
tool to interact with the SlackBuilds.org (``SBo'') repository, a
collection of third-party SlackBuild scripts to build Slackware
packages.
<A NAME="lbAE">&nbsp;</A> <A NAME="lbAE">&nbsp;</A>
<H2>INSTRUCTIONS</H2> <H3>Instructions</H3>
Sbopkg usage assumes an understanding of SlackBuild scripts, <B>Sbopkg</B>
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. usage assumes an understanding of SlackBuilds, generally, and the
third-party SBo repository, specifically.
A thorough reading of
<I><A HREF="http://www.slackbuilds.org/howto/">http://www.slackbuilds.org/howto/</A></I>
and the pages at
<I><A HREF="http://www.slackwiki.org">http://www.slackwiki.org</A></I>
about SlackBuilds is strongly advised.
<P> <P>
Sbopkg can be run from the command line by simply invoking &quot;sbopkg.&quot;
Sbopkg must be run as the root user (since the SlackBuild scripts at In order for
SlackBuilds.org are written with the intention of being run as root). <B>sbopkg</B>
Furthermore, using 'su -' instead of 'su' is strongly encouraged.
The reason is that some SlackBuild scripts rely on certain tools that to be used, a configuration file must exist at
are only available in root's $PATH when root's $PATH is inherited <I>/etc/sbopkg/sbopkg.conf</I>.
(i.e. texmf to build man pages) and root's $PATH is not inherited when
only using 'su'. In any evnet, invoking 'sbopkg' from the command An initial install will provide the user with that file while upgrades
line will launch the dialog-based interface, and the menus provided will add an
should be fairly self-explanatory. The main menu allows the user to <I>/etc/sbopkg/sbopkg.conf.new</I>
rsync with the SlackBuilds.org repository (currently, the size of a
local copy of the SBo repository is less than 50MB), view the which may be merged with or replace the older version.
SlackBuilds.org Changelog, check for potential updates to SBo See
packages, display the contents of the local cache directory where <B><A HREF="http://localhost/cgi-bin/man/man2html?5+sbopkg.conf">sbopkg.conf</A></B>(5)
source tarballs are saved, display the permanent build log, and browse
or search the local copy of the SBo repository. Once the browse for more information about the configuration file.
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 chose. 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> <P>
Alternatively, sbopkg can be run from the command line without using
the dialog interface. Executing &quot;sbopkg -h&quot; will display a list of <B>Sbopkg</B>
options available from the command line.
must be run as the root user (since the SBo SlackBuilds are written with
the intention of being run as root).
Furthermore, using the
<B>-</B>
option with
<B>su</B>
is strongly encouraged.
The reason is that some SlackBuilds rely on certain tools that are only
available in root's
<B>PATH</B>
when the scripts in
<I>/etc/profile.d</I>
have been run (i.e.,
<B>texmf</B>
to build man pages), which is only done for login shells, or otherwise
require a ``truer'' root environment than that given by only
<B>su</B>.
In any event, invoking
<B>sbopkg</B>
with no arguments (or with just
<B>-d</B>,
<B>-f</B>,
or
<B>-V</B>)
will launch the
<B>dialog</B>-based
interface, and the menus provided should be fairly self-explanatory.
<P> <P>
Sbopkg also has the capability of loading, saving, and using
user-created queuefiles. These queuefiles are simple text files with The main menu allows the user to synchronize with the SBo repository.
one application name per line. By default, when a queuefile is loaded This is the first step to take (after configuration) with a new install
in the dialog interface, the application is selected, or &quot;ON.&quot; This of
can be changed by inserting a &quot;-&quot; in front of the application name in <B>sbopkg</B>.
the queuefile. Also, queuefiles can reference other queuefiles when
the first character is a &quot;@&quot;. See the readme-queuefiles document in Currently, the size of a local copy of the SBo repository is about
the doc/ directory for more information. about 90MB.
The main menu also allows the user to view the SBo
<I>ChangeLog</I>,
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
<I>README</I>,
<I>SlackBuild</I>,
<I>.info</I>,
or
<I>slack-desc</I>
files.
The user can also edit the
<I>.info</I>
file and
<I>SlackBuild</I>
and the edited files will remain after doing a sync.
Additionally, the user can choose to build a package using either the
original
<I>SlackBuild</I>
or the locally-edited one, if present.
If using the
<B>dialog</B>
interface, and if
<B>sbopkg</B>
finds a built package for a particular piece of software in the
<B>OUTPUT</B>
directory, then
<B>sbopkg</B>
will automatically add a new menu entry allowing the user to install the
package if he chooses.
Alternatively, the user can choose to automatically build, or both build
and install, individual packages or several packages in a build queue.
Finally, if
<B>KEEPLOG</B>
is set to
<B>YES</B>
in the
<I>sbopkg.conf</I>
file then a permanent log of the build process is saved.
See
<B><A HREF="http://localhost/cgi-bin/man/man2html?5+sbopkg.conf">sbopkg.conf</A></B>(5)
under
<B>KEEPLOG</B>
and
<B>LOGFILE</B>
for details.
<P> <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 Alternatively,
an editor to edit the .info or SlackBuild files. The pager function <B>sbopkg</B>
will look to the environmental variable $PAGER and if that variable is
not defined then it will default to 'more.' Similarly, the edit can be run from the command line without using the
function found when sbopkg is used with the dialog interface will look <B>dialog</B>
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 interface.
adding the requisite information in ~/.bashrc, /etc/profile, or other See the
similar configuration file to export $EDITOR will suffice. <B>OPTIONS</B>
section for the available command line options.
<P> <P>
<B>Sbopkg</B>
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 an ``@''.
See the
<I>readme-queuefiles</I>
document in the documentation directory for more information.
<P>
Certain features of
<B>sbopkg</B>
rely on outside binaries, such as a pager to view the text files when
<B>sbopkg</B>
is run from the command line, and an editor to edit the
<I>.info</I>
or
<I>SlackBuild</I>
files.
The paging functions will look to the environmental variable
<B>PAGER</B>
and, if that variable is not defined, it will default to
<B>more</B>.
Similarly, the editing functions will look to
<B>EDITOR</B>
and will default to
<B>vi</B>.
If the user wants
<B>sbopkg</B>
to use another editor, such as
<B>nano</B>,
then adding the requisite information in
<I>~/.bashrc</I>,
<I>/etc/profile</I>,
or other similar configuration file to export
<B>EDITOR</B>
will suffice.
<A NAME="lbAF">&nbsp;</A> <A NAME="lbAF">&nbsp;</A>
<H2>OPTIONS</H2> <H2>OPTIONS</H2>
<DL COMPACT> <DL COMPACT>
<DT><B>-b PACKAGE(s)/QUEUE(s)</B> <DT><B>-b</B><I> PACKAGE(s)/QUEUE(s)</I>
<DD> <DD>
Search for and build PACKAGE(s) from the local SBo repository. If more Build packages of the argument(s) from the active repository.
than one package is specified, they must be in quotes. For example: If more than one package is specified, they may either be quoted or the
<P> switch can be given multiple times.
#sbopkg -b &quot;foo bar&quot; Using this second form, a colon-separated list of options may be given.
<P> If whitespace occurs between the colons, it must be quoted.
will build foo and then bar. <DT><DD>
Queuefile names can also be specified. In that case, all the packages For example:
specified in the queuefile will be built. In the unfortunate case a <DL COMPACT><DT><DD>
token matches both a queuefile name and a package name (i.e. the user <DL COMPACT>
named a queuefile with the name of a package), sbopkg will ask the user <DT><DD>
which one should be used. The tokens (package names or queuefiles) <PRE>
are processed in the order they are specified on the command line, and # sbopkg -b &quot;foo bar&quot;
the build order specified in the queuefiles is retained. If a package </PRE>
is specified more than once, it gets queued only the first time it is
encountered. </DL>
<P> </DL>
<DT><DD>
will build
<I>foo</I>
and then
<I>bar</I>.
<DT><DD>
Or
<DL COMPACT><DT><DD>
<DL COMPACT>
<DT><DD>
<PRE>
# sbopkg -b app1:opt1=&quot;foo bar&quot;:opt2=baz -b app2:opt=mu
</PRE>
</DL>
</DL>
<DT><DD>
will build app1 with the options ``foo bar'' and ``baz'', and app2 with
the option ``mu''.
<DT><DD>
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),
<B>sbopkg</B>
will ask the user which one should be used.
A way to avoid this is to specify the queuefile with its
<I>.sqf</I>
extension.
Also, a mix of both packages and queuefiles may be given.
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.
<DT><B>-c</B> <DT><B>-c</B>
<DD> <DD>
Display list of installed SBo packages and potential updates. Display a list of installed SBo packages and potential updates.
<P>
<DT><B>-d DIRECTORY</B> <DT><B>-d</B><I> DIRECTORY</I>
<DD> <DD>
Manually specify the full path to the DIRECTORY containing the Manually specify the full path to the
local SBo repository. <I>DIRECTORY</I>
<P>
<DT><B>-e ask|continue|stop</B> containing the local SBo repository.
<DT><B>-e ask</B>|continue|stop
<DD> <DD>
Specify what sbopkg should do when it encounters an error while building a Specify what
package. Valid options are: <B>sbopkg</B>
<P>
<B>ask</B>
: This is the default behavior, asking the user what to do; should do when it encounters an error while building a package.
<P> Valid options are:
<B>continue</B> <DT><DD>
<B>ask</B>:
: Ignore the error and continue processing (act as if the user This is the default behavior, asking the user what to do.
answered &quot;Yes&quot; to all questions); <DT><DD>
<P> <B>continue</B>:
<B>stop</B>
: Stop the processing (act as if the user answered &quot;No&quot; to all Ignore the error and continue processing (act as if the user answered
questions). ``Yes'' to all questions).
<P> <DT><DD>
<DT><B>-f</B> <B>stop</B>:
Stop the processing (act as if the user answered ``No'' to all questions).
<DT><B>-f</B><I> FILE</I>
<DD> <DD>
Override the default configuration file, which is located by Override the default configuration file,
default at /etc/sbopkg/sbopkg.conf, with another configuration <I>/etc/sbopkg/sbopkg.conf</I>,
file.
<P> with
<DT><B>-g PACKAGE(s)</B> <I>FILE</I>.
<DT><B>-g</B><I> PACKAGE(s)</I>
<DD> <DD>
General search for PACKAGE(s) by glob. For example: General search for
<P> <I>PACKAGE(s)</I>
#sbopkg -g nv
<P> by case-insensitive glob where the argument is automatically wrapped in
will return a list of matches, such as the nvidia packages, <B>*</B>s.
konversation, and other packages with 'nv' in their name. If more
than one glob is specified, they must be in quotes. If more than one glob is specified, they must be quoted or the -g flag
<P> must be used multiple times, once for each glob.
<DT><DD>
For example:
<DL COMPACT><DT><DD>
<DL COMPACT>
<DT><DD>
<PRE>
# sbopkg -g &quot;foo bar&quot;
</PRE>
</DL>
</DL>
<DT><DD>
will return a list of packages with either
<I>foo</I>
or
<I>bar</I>
in their names.
<DT><B>-h</B> <DT><B>-h</B>
<DD> <DD>
Display the help. Display the help.
<P>
<DT><B>-i PACKAGE(s)</B> <DT><B>-i</B><I> PACKAGE(s)/QUEUE(s)</I>
<DD> <DD>
Search for and build and then install PACKAGE(s) from the local SBo Build and install packages of the argument(s) from the active
repository. If more than one package is specified, they must be in repository.
quotes, and the packages will be built and then installed in the <DT><DD>
listed order. For example: See the
<P> <B>-b</B>
#sbopkg -i &quot;foo bar&quot;
<P> option for details since, other than the installation, these two options
will build and install foo and then build and install bar. By operate similarly.
carefully considering the order of the packages listed, the user may <DT><DD>
be able to build and install dependencies in the right order before Note that by carefully considering the order of the packages listed, the
the final application is built and installed. Of course, given the user may be able to build and install dependencies in the right order
nature of dependencies, this may not always be possible and so before the final application is built and installed.
building dependencies like this is not really a supported feature. Of course, given the nature of dependencies, this may not always be
Still, when when it works, it can be helpful. possible and so building dependencies like this is not really a
<P> supported feature.
Queuefile names are supported, too. See the explanation for the '-b' Still, when it works, it can be helpful.
command for details.
<P>
<DT><B>-k</B> <DT><B>-k</B>
<DD> <DD>
When used together with -b or -i, this option tells sbopkg to skip When used together with
(i.e. don't build) any package it finds to be already installed. <B>-b</B>
<P>
or
<B>-i</B>,
this option tells
<B>sbopkg</B>
to skip (i.e., don't build) any package it finds to be already
installed.
<DT><DD>
Please note that only a name comparison is performed, so when this Please note that only a name comparison is performed, so when this
option is specified sbopkg will also omit the build of different option is specified
versions of installed packages. <B>sbopkg</B>
<P>
will also omit the build of different versions of installed packages.
<DT><B>-l</B> <DT><B>-l</B>
<DD> <DD>
Display the SBo ChangeLog.txt and quit. Display the SBo
<P> <I>ChangeLog</I>
and quit.
<DT><B>-o</B> <DT><B>-o</B>
<DD> <DD>
List the currently installed cached source files which are deemed as List the currently installed cached source files which are deemed
obsolete, and optionally delete them. obsolete, and optionally delete them.
<P> <DT><DD>
Source files are obsolete when no SBo script references it any more, Source files are obsolete when no
which is something that can happen after rsync-ing the local <I>.info</I>
repository.
<P> file's
Please note that only the currently active repository is <B>DOWNLOAD</B>
used to identify the obsoleted sources, so if you build packages with
different repositories (e.g. for different Slackware versions) the field(s) reference it any more, which is something that can happen after
source files only used in the &quot;other&quot; repository will be listed. syncing the local repository.
<P> <DT><DD>
Please note that only the currently active repository is used to
identify the obsolete sources, so if the user builds packages with
different repositories (e.g., for different Slackware versions) the
source files only used in the ``other'' repository will be listed.
<DT><B>-P</B> <DT><B>-P</B>
<DD> <DD>
List the cached package files which are not currently installed on the List the cached package files which are not currently installed on the
system and optionally delete them. system and optionally delete them.
<P>
<DT><B>-p</B> <DT><B>-p</B>
<DD> <DD>
List installed SlackBuilds.org packages. List installed SBo packages.
<P>
<DT><B>-q</B> <DT><B>-q</B>
<DD> <DD>
Enable the &quot;quiet mode.&quot; When this flag is specified, the output of Enable the ``quiet mode.''
some of the command-line options is minimized. When this flag is specified, the output of some of the command-line
<P> options is minimized.
<DT><B>-r</B>
<DD>
Rsync the local repository with SlackBuilds.org and quit.
<P>
<DT><B>-R</B> <DT><B>-R</B>
<DD> <DD>
Show all the README files of the queued packages before starting the build. Show all the
This is useful when you want to make a final check. <I>README</I>
<P>
<DT><B>-s PACKAGE(s)</B> files of the queued packages before starting the build.
This is useful when the user wants to make a final check.
<DT><B>-r</B>
<DD> <DD>
Specific search for PACKAGE(s) by PACKAGE name and, if found, display ``Rsync'' the local repository with SBo and quit.
the README, SlackBuild, .info, and slack-desc files in that order
using $PAGER, which defaults to 'more' as described above. If more <DT><B>-s</B><I> PACKAGE(s)</I>
than one package is specified, they must be in quotes. For example:
<P> <DD>
#sbopkg -s &quot;foo bar&quot; Specific search for
<P> <I>PACKAGE(s)</I>
will search for foo and then bar.
<P> by case-sensitive glob and, if found, display the
<I>README</I>,
<I>SlackBuild</I>,
<I>.info</I>,
and
<I>slack-desc</I>
files in that order for each
<I>PACKAGE</I>
found, using
<I>$PAGER</I>.
If more than one glob is specified, they must be quoted or the -s flag
must be used multiple times, once for each glob.
<DT><DD>
For example:
<DL COMPACT><DT><DD>
<DL COMPACT>
<DT><DD>
<PRE>
# sbopkg -s &quot;foo bar&quot;
</PRE>
</DL>
</DL>
<DT><DD>
will display all the above-mentioned files for packages whose names are
exactly
<I>foo</I>
or
<I>bar</I>.
<DT><DD>
Note that shell metacharacters may be supplied in the arguments. For
instance,
<DL COMPACT><DT><DD>
<DL COMPACT>
<DT><DD>
<PRE>
# sbopkg -s '*[Oo]pen*'
</PRE>
</DL>
</DL>
<DT><DD>
will return all packages with 'open' or 'Open' anywhere in the name.
If multiple applications are returned, the user will be presented with a
menu to select from.
<DT><B>-u</B> <DT><B>-u</B>
<DD> <DD>
Check for an update to sbopkg itself and then quit. Check for an update to
<P> <B>sbopkg</B>
<DT><B>-V REPO/BRANCH</B>
itself and then quit.
<DT><B>-V</B><I> VERSION</I>
<DD> <DD>
Set the repository and branch to use. Set the repository and branch to use.
<P> <DT><DD>
For a list of valid versions, invoke sbopkg as For a list of valid versions, invoke
<B>sbopkg -V ?</B>. <B>sbopkg</B>
as
<DL COMPACT><DT><DD>
<DL COMPACT>
<DT><DD>
<PRE>
# sbopkg -V ?
</PRE>
</DL>
</DL>
<DT><DD>
See the See the
<B>sbopkg.conf (5)</B> <B><A HREF="http://localhost/cgi-bin/man/man2html?5+sbopkg.conf">sbopkg.conf</A></B>(5)
man page for more information about the ``local'' repository.
<DT><DD>
The
<I>VERSION</I>
format is repository/branch (e.g., SBo/13.1).
If the repository is omitted,
<B>sbopkg</B>
will first look for the specified branch in the default repository.
If that attempt fails,
<B>sbopkg</B>
will look for the first matching branch in any repository.
man page for more information about the 'local' repository.
<P>
The VERSION format is repository/branch (e.g. SBo/13.1). 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>
<DT><B>-v</B> <DT><B>-v</B>
<DD> <DD>
Prints the current version of sbopkg on stdout. Prints the current version of
<P> <B>sbopkg</B>
on stdout.
</DL> </DL>
<A NAME="lbAG">&nbsp;</A> <A NAME="lbAG">&nbsp;</A>
<H2>FILES</H2> <H2>FILES</H2>
<B>/etc/sbopkg/sbopkg.conf</B> <DL COMPACT>
<DT><I>/etc/sbopkg/sbopkg.conf</I>
&nbsp;- File to specify configuration options. <DD>
<P> Default system-wide file to specify configuration options.
<B>/etc/sbopkg/renames.d/50-default</B> <DT><I>/etc/sbopkg/renames.d/50-default</I>
&nbsp;- Default file that lists software in SBo repository that has been renamed. <DD>
See the README-renames.d document in the sbopkg doc/ directory for more Default file that lists software in the SBo repositories that has been
information. renamed.
<P> See the
<B>/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo}</B> <I>README-renames.d</I>
&nbsp;- Three default files for various types of sbopkg repositories. See the document in the
README-repos.d document in the sbopkg doc/ directory for more information. <B>sbopkg</B>
<P>
documentation directory for more information.
<DT><I>/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo}</I>
<DD>
Three default files for various types of
<B>sbopkg</B>
repositories.
See the
<I>README-repos.d</I>
document in the
<B>sbopkg</B>
documentation directory for more information.
</DL>
<A NAME="lbAH">&nbsp;</A> <A NAME="lbAH">&nbsp;</A>
<H2>SEE ALSO</H2> <H2>AUTHORS</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">&nbsp;</A>
<H2>AUTHOR</H2>
Chess Griffin Chess Griffin
&lt;<A HREF="mailto:chess@chessgriffin.com">chess@chessgriffin.com</A>&gt; &lt;<A HREF="mailto:chess@chessgriffin.com">chess@chessgriffin.com</A>&gt;
<P> <P>
Mauro Giachero
&lt;<A HREF="mailto:mauro.giachero@gmail.com">mauro.giachero@gmail.com</A>&gt;
<P>
slakmagik
&lt;<A HREF="mailto:slakmagik@gmail.com">slakmagik@gmail.com</A>&gt;
<A NAME="lbAI">&nbsp;</A>
<H2>SEE ALSO</H2>
<B><A HREF="http://localhost/cgi-bin/man/man2html?1+dialog">dialog</A></B>(1),
<B><A HREF="http://localhost/cgi-bin/man/man2html?1+more">more</A></B>(1),
<B><A HREF="http://localhost/cgi-bin/man/man2html?8+removepkg">removepkg</A></B>(8),
<B><A HREF="http://localhost/cgi-bin/man/man2html?1+rsync">rsync</A></B>(1),
<B><A HREF="http://localhost/cgi-bin/man/man2html?5+sbopkg.conf">sbopkg.conf</A></B>(5),
<B><A HREF="http://localhost/cgi-bin/man/man2html?1+su">su</A></B>(1),
<B><A HREF="http://localhost/cgi-bin/man/man2html?8+upgradepkg">upgradepkg</A></B>(8),
<B><A HREF="http://localhost/cgi-bin/man/man2html?1+vi">vi</A></B>(1),
<I>/usr/doc/sbopkg-0.34.0/*</I>
<P>
<HR> <HR>
<A NAME="index">&nbsp;</A><H2>Index</H2> <A NAME="index">&nbsp;</A><H2>Index</H2>
<DL> <DL>
<DT><A HREF="#lbAB">NAME</A><DD> <DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">SYNOPSIS</A><DD> <DT><A HREF="#lbAC">SYNOPSIS</A><DD>
<DT><A HREF="#lbAD">DESCRIPTION</A><DD> <DT><A HREF="#lbAD">DESCRIPTION</A><DD>
<DT><A HREF="#lbAE">INSTRUCTIONS</A><DD> <DL>
<DT><A HREF="#lbAE">Instructions</A><DD>
</DL>
<DT><A HREF="#lbAF">OPTIONS</A><DD> <DT><A HREF="#lbAF">OPTIONS</A><DD>
<DT><A HREF="#lbAG">FILES</A><DD> <DT><A HREF="#lbAG">FILES</A><DD>
<DT><A HREF="#lbAH">SEE ALSO</A><DD> <DT><A HREF="#lbAH">AUTHORS</A><DD>
<DT><A HREF="#lbAI">AUTHOR</A><DD> <DT><A HREF="#lbAI">SEE ALSO</A><DD>
</DL> </DL>
<HR> <HR>
This document was created by This document was created by
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>, <A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR> using the manual pages.<BR>
Time: 18:31:58 GMT, May 27, 2010 Time: 03:40:11 GMT, November 12, 2010
</BODY> </BODY>
</HTML> </HTML>