From dac7bd21c9296078b3c976af52f54cf2611312c9 Mon Sep 17 00:00:00 2001 From: slakmagik Date: Fri, 12 Nov 2010 04:07:45 +0000 Subject: [PATCH] tag and release 0.34.0 --- src/usr/doc/ChangeLog.txt | 4 +- tools/ChangeLog-latest.txt | 84 +-- tools/current-download | 2 +- tools/current-package | 2 +- tools/current-source | 2 +- tools/current-version | 2 +- tools/sbopkg-conf5.html | 1009 ++++++++++++++++++++++++------------ tools/sbopkg-help | 8 +- tools/sbopkg.SlackBuild | 2 +- tools/sbopkg8.html | 842 +++++++++++++++++++++--------- 10 files changed, 1351 insertions(+), 606 deletions(-) diff --git a/src/usr/doc/ChangeLog.txt b/src/usr/doc/ChangeLog.txt index 5185365..3df8740 100644 --- a/src/usr/doc/ChangeLog.txt +++ b/src/usr/doc/ChangeLog.txt @@ -1,5 +1,5 @@ -Thu May 27 18:13:59 UTC 2010 -Sbopkg X.XX.X released. This version contains the following fixes and +Fri Nov 12 03:37:16 UTC 2010 +Sbopkg 0.34.0 released. This version contains the following fixes and enhancements: * Revised man pages - these are very different and now document a couple of diff --git a/tools/ChangeLog-latest.txt b/tools/ChangeLog-latest.txt index 2ae13a1..87c4ce8 100644 --- a/tools/ChangeLog-latest.txt +++ b/tools/ChangeLog-latest.txt @@ -1,41 +1,49 @@ -Thu May 27 18:13:59 UTC 2010 -Sbopkg 0.33.1 released. This version contains the following fixes and +Fri Nov 12 03:37:16 UTC 2010 +Sbopkg 0.34.0 released. This version contains the following fixes and enhancements: - * The ARCH assignment was modified to accord with the latest SBo SlackBuild - template. - * Tweaked widgets in select_repository() (no or less scrolling) and - load_user_queue() (better button) and modified check_gpg() to not disrupt - the dialog interface with gpg output - * Revised the KNOWN_ISSUES file and other documentation -+--------------------------+ -Mon May 24 20:53:43 UTC 2010 -Sbopkg 0.33.0 released. This version contains the following fixes and -enhancements: - - * Addressed an apparent bash 4.1 bug that causes the 'obsolete sources' - function to break. - * Addressed issue 44 where hitting ^C during the download of part of a queue - and restarting the queue could result in a download failure. Thanks to - slava18 for the report. - * Changed the menu order of the "Build options" dialog to default to using - "Saved" options rather than "None". - * Fixed issue 45 where packages with '+' in the name were not properly - detected in some cases. Thanks to skalkoto for the report. - * Added a help item to the main menu of the dialog interface with pointers - to documentation and other resources. - * Added an option to print the version of sbopkg. We try not to change the - meaning of flags but note that this does change what was the '-v' flag to - '-V' and now uses '-v' for its customary 'version' purpose. Note that the - new -V flag now accepts a '?' argument (sbopkg -V ?) which will display - the list of valid repositories. - * Tweak the logic re determining ARCH and modify some ARCH-related - evals and conditionals in check_for_updates and info_item. - * Fixed a bug which could result in some sources being missed when checking - for obsolete sources. - * Added a command line option '-P' to access the 'remove uninstalled - packages' function which had previously only been accessible from the - dialog interface. - * Miscellaneous tweaks in preparation for release and to bring in line with - Slackware 13.1. + * Revised man pages - these are very different and now document a couple of + previously undocumented things and are worth a (re-)read. Thanks to + Marie-Claude Collilieux for the French translations of these. + * The HACKING file now includes a man page style guide in addition to the + coding style guide. + * The LOGDIR variable has been removed from sbopkg.conf - DIR can be + specified in LOGFILE. + * The DEBUG variable has been renamed to DEBUG_UPDATES in sbopkg.conf. + * The default timeout values in {WGET,RSYNC}FLAGS have been raised from + 10/15 to 30 in sbopkg.conf. + * All parameters in sbopkg.conf now use default values only if the variable + hasn't been previously set (meaning they can all be overridden by passing + variables on the command line). + * sbopkg.conf has been reordered - this may make any merging that may be + needed more interesting this time but hopefully it's worth it. + * The directory initialization process has been changed - at first run or + otherwise when encountering missing directories, the user will now be + presented with a single list of them and a (C)reate/(A)bort prompt. + * The command line user interface has been overhauled in terms of more + consistent validated command line messages and prompts. + * Fix an ARCH display issue in the updates screen; thanks to alkos333, Marc + Payne, and David Spencer for confirming the issue and thanks to David + Spencer for testing the fix. + * Fixed bugs with dzen2 and *zarafa* not downloading/building properly. Note + that, while the changes fix these issues and should make it easier to + handle similar problems in the future, this change may introduce + regressions. If a download or build fails due to a downloaded tarball + looking something like 'blah?actual_tarball.tar.gz' or the like, please + report it to us. + * Fixed bugs with the '-s' option where only the first of multiple + arguments would be returned and where the command line select menu was + broken. Also where it and the -g flag might inadvertently expand globs + wrongly. + * It's now possible to specify the b,g,i,s flags multiple times. Previously + multiple arguments to these flags had to be quoted (-b "foo bar") but now + 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. +--------------------------+ diff --git a/tools/current-download b/tools/current-download index 47dbf89..3de667b 100644 --- a/tools/current-download +++ b/tools/current-download @@ -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 diff --git a/tools/current-package b/tools/current-package index 618533b..a89d907 100644 --- a/tools/current-package +++ b/tools/current-package @@ -1 +1 @@ -sbopkg-0.33.2-noarch-1_cng.tgz +sbopkg-0.34.0-noarch-1_cng.tgz diff --git a/tools/current-source b/tools/current-source index 93d1903..f315baa 100644 --- a/tools/current-source +++ b/tools/current-source @@ -1 +1 @@ -sbopkg-0.33.2.tar.gz +sbopkg-0.34.0.tar.gz diff --git a/tools/current-version b/tools/current-version index c9ec1d5..85e60ed 100644 --- a/tools/current-version +++ b/tools/current-version @@ -1 +1 @@ -0.33.2 +0.34.0 diff --git a/tools/sbopkg-conf5.html b/tools/sbopkg-conf5.html index 24f252c..85b8777 100644 --- a/tools/sbopkg-conf5.html +++ b/tools/sbopkg-conf5.html @@ -3,393 +3,758 @@ Content-type: text/html Manpage of SBOPKG.CONF

SBOPKG.CONF

-Section: (5)
Updated: May 2010
Index +Section: (5)
Updated: November 2010
Index Return to Main Contents
+  

NAME

-sbopkg.conf +sbopkg.conf - configuration file for sbopkg -- Configuration file for sbopkg -

 

DESCRIPTION

-

-The sbopkg.conf file contains configuration settings for -sbopkg +The +sbopkg.conf + +file contains configuration settings for +sbopkg(8), + +a tool for interacting with the SlackBuilds.org (``SBo'') repository, a +collection of third-party SlackBuild scripts to build Slackware +packages. +The default configuration file is installed at +/etc/sbopkg/sbopkg.conf. + +Also, please see the subsection below about +ARCH. -(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.

-Boolean options are case-insensitive. -

-The different configuration options are: + +All boolean options require a +YES + +or a +NO + +without regard to case. +All path values must be full.

+ +The default configuration options are: +

-
REPO_NAME - -
-
- -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. -

-The default value of REPO_NAME is: -
- -REPO_NAME=${REPO_NAME:-SBo}. -

-

REPO_BRANCH - -
-
- -This option allows the user to set the default active repository -branch. The current options are 11.0, 12.0, 12.1, 12.2, 13.0, and -13.1 for the SBo repository and local for the local repository. The -Slamd64Builds repository is 'master' but is not officially supported. -

-The default value of REPO_BRANCH is: -
- -REPO_BRANCH=${REPO_BRANCH:-13.1}. -

-

REPO_ROOT - -
-
- -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. -

-The default value of REPO_ROOT is: -
- -REPO_ROOT=${REPO_ROOT:-/var/lib/sbopkg}. -

-

SRCDIR - -
-
- -This option contains the location of the cache directory where -source downloads will be saved. -

-The default value of SRCDIR is: -
- -SRCDIR=${SRCDIR:-/var/cache/sbopkg}. -

-

SBOPKGTMP - -
-
- -This option sets the default directory where certain working -files are saved on a temporary basis. -

-The default value of SBOPKGTMP is: -
- -SBOPKGTMP=${SBOPKGTMP:-/tmp/sbopkg}. -

-

TMP - -
-
- -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. -

-The default value of TMP is: -
- -export TMP=${TMP:-/tmp/SBo}. -

-

OUTPUT - -
-
- -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. -

-The default value of OUTPUT is: -
- -export OUTPUT=${OUTPUT:-/tmp}. -

-

QUEUEDIR - -
-
- -This option defines the directory under which saved queue files will -be kept. -

-The default value of QUEUEDIR is: -
- -QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}. -

-

KEEPLOG - -
-
- -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. -

-The default value of KEEPLOG is: YES. -

-

LOGDIR - -
-
- -This option sets the location for the sbopkg permanent log if KEEPLOG -is set to YES (see previous paragraph). -

-The default value of LOGDIR is: -
- -LOGDIR=${LOGDIR:-/var/log/sbopkg}. -

-

CLEANUP - -
-
- -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. -

-The default value of CLEANUP is: NO. -

ALLOW_MULTI
-
+Boolean. +
+When set to +YES, -When set to YES, this option allows the user to run multiple instances -of sbopkg. -

+this option allows the user to run multiple instances of +sbopkg + +simultaneously. +

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. -

+you should consider this an EXPERIMENTAL UNSUPPORTED feature. +If you encounter problems, please try to make sure these aren't caused +by yourself doing improper things. +

For reference, these are some of the things you shouldn't do with this option enabled:
-
[bu]
-run an ALLOW_MULTI=NO instance together with one or more having -ALLOW_MULTI=YES -
[bu]
+
*
+run instances with a mixture of +YES + +and +NO + +settings +
*
sync a repository when another instance is using it -
[bu]
+
*
change the branch of a git repository when another instance is using it -(you can do this with rsync -- i.e. SlackBuild.org -- repos) -
[bu]
-simultaneously build or install the same package from different instances -
[bu]
+(this caveat does not apply to rsync repositories) +
*
+simultaneously build or install the same package from different +instances +
*
save a queue file while using it from another instance
-

-

-There can be more unsafe situations we haven't thought about. Take care. -
+
+There can be more unsafe situations we haven't thought about. +Take care. +
+The default assignment is: +
+ALLOW_MULTI=${ALLOW_MULTI:-NO} -

-

DEBUG +
CLEANUP
-
+Boolean. +
+When set to +YES, -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. -

-The default value of DEBUG is: 0. -

-

MKDIR_PROMPT +the unpacked source files and package tree in +$TMP + +are deleted right after the build, though the downloaded source archive +and completed package are left in +$SRCDIR + +and +$OUTPUT. + +
+A side effect of setting +CLEANUP + +to +YES + +is that +TMP + +is set to an internal value and any other +TMP + +setting is ignored. +
+The default assignment is: +
+CLEANUP=${CLEANUP:-NO} + +
DEBUG_UPDATES
-
+Enumeration. +
+This option should be set to +0, -This option may be set to YES or NO. When set to YES, sbopkg will prompt -for confirmation before changing the filesystem by creating its -directories. If you do not wish to be prompted (for instance, if you -have some of the directories on a temporary filesystem and don't wish to -be prompted for confirmation each time the filesystem is reinitialized) -you can set this to NO. -

-The default value of MKDIR_PROMPT is: YES. -

-

RSYNCFLAGS +1, -
-
+or +2. -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. -

-The default value of RSYNCFLAGS is: "--timeout=10 --verbose". -

-

WGETFLAGS +DEBUG_UPDATES -
-
+sets the default debugging level for the update list feature of +sbopkg. -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. -

-The default value of WGETFLAGS is: -
+When set to +0, + +only potential updated (or downgraded) packages are listed. +When set to +1, + +potential updates plus packages not in the repo and packages that are +newer than the repo are listed. +When set to +2, + +all non-updated packages are also listed. +Changing +DEBUG_UPDATES + +to +1 + +or +2 + +may be helpful if it appears the updatelist might be missing an update. +

+The default assignment is: +
+DEBUG_UPDATES=${DEBUG_UPDATES:-0} -"--continue --progress-bar:force --timeout=15 --tries=5". -

DIFF
-
- +Command. +
This option allows the user to set which diff program to use when -sbopkg displays differences between edited files. -

-The default value of DIFF is: -
+sbopkg + +displays differences between edited files. +

+The default assignment is: +
+DIFF=${DIFF:-diff} -DIFF=${DIFF:-diff}. -

DIFFOPTS
-
+Command options. +
+This option allows the user to set which options are used by the +$DIFF -This option allows the user to set which options are used by the $DIFF -program when sbopkg displays differences between edited files. -

-The default value of DIFFOPTS is: -

+program when +sbopkg + +displays differences between edited files. +

+The default assignment is: +
DIFFOPTS=${DIFFOPTS:--u} -

+ +

KEEPLOG + +
+Boolean. +
+This option allows the user to choose whether to keep a permanent log of +packages that are built with +sbopkg + +in order to review the builds for historical or troubleshooting +purposes. +See +LOGFILE + +for the location of this log. +
+The default assignment is: +
+KEEPLOG=${KEEPLOG:-YES} + +
LOGFILE + +
+Path. +
+This option sets the name for the build log if +KEEPLOG + +is set to +YES. + +
+The default assignment is: +
+LOGFILE=${LOGFILE:-/var/log/sbopkg/sbopkg-build-log} + +
MKDIR_PROMPT + +
+Boolean. +
+When set to +YES, + +sbopkg + +will prompt for confirmation before changing the filesystem by creating +its directories. +If you do not wish to be prompted (for instance, if you have some of the +directories on a temporary filesystem and don't wish to be prompted for +confirmation each time the filesystem is reinitialized) you can set this +to +NO. + +
+The default assignment is: +
+MKDIR_PROMPT=${MKDIR_PROMPT:-YES} + +
OUTPUT + +
+Path. +
+This option sets the default directory where compiled packages are +saved. +OUTPUT + +must be exported as it is also used by the SBo SlackBuilds. +Note that the default value of +OUTPUT + +is therefore the same as in the SBo SlackBuilds. +
+The default assignment is: +
+export OUTPUT=${OUTPUT:-/tmp} + +
QUEUEDIR + +
+Path. +
+This option defines the directory under which saved queue files will be +kept. +
+The default assignment is: +
+QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues} + +
REPO_BRANCH + +
+Enumeration. +
+This option allows the user to set the default active repository branch. +The current standard values are listed in the default +repos.d/* + +files and can also be listed by issuing +
+
+
+
+# sbopkg -V ?
+
+ +
+
+ +
+The default assignment is: +
+REPO_BRANCH=${REPO_BRANCH:-13.1} + +
REPO_NAME + +
+Enumeration. +
+This option allows the user to choose the repository to use. +See +REPO_BRANCH + +for how to get an enumeration of standard values. +The ``local'' choice corresponds to a user-maintained repository whose +structure must be the same as the one used by SBo, in the sense of a +category/package/files + +hierarchy. +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 + +documentation directory. +
+The default assignment is: +
+REPO_NAME=${REPO_NAME:-SBo} + +
REPO_ROOT + +
+Path. +
+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 about 90MB. +
+The default assignment is: +
+REPO_ROOT=${REPO_ROOT:-/var/lib/sbopkg} + +
RSYNCFLAGS + +
+Command options. +
+Rsync + +is used by +sbopkg + +to mirror the SBo 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 those internal default options is not recommended. +However, +--timeout + +is a useful option to play with if getting syncing errors. +
+The default assignment is: +
+RSYNCFLAGS="${RSYNCFLAGS:---verbose --timeout=30}" + +
SBOPKGTMP + +
+Path. +
+This option sets the default directory where certain working files +specific to +sbopkg + +are saved on a temporary basis. +
+The default assignment is: +
+xxxSBOPKGTMPxxx + +
SRCDIR + +
+Path. +
+This option contains the location of the cache directory where source +downloads will be saved. +
+The default assignment is: +
+SRCDIR=${SRCDIR:-/var/cache/sbopkg} + +
TMP + +
+Path. +
+This option sets the default directory where built packages are saved. +TMP + +must be exported as it is also used by the SBo SlackBuilds. +Note that the default value of +TMP + +is therefore the same as in the SBo SlackBuilds. +
+Also note that if the +CLEANUP + +variable is set to +YES, + +any custom +TMP + +setting is ignored. +
+The default assignment is: +
+export TMP=${TMP:-/tmp/SBo} + +
WGETFLAGS + +
+Command options. +
+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 most of these default options is not recommended. +However, +--timeout + +is a useful option to play with if getting download errors. +
+The default assignment is: +
+WGETFLAGS="${WGETFLAGS:--c --progress=bar:force --timeout=30 --tries=5}" +
  -

OVERRIDING ENVIRONMENTAL VARIABLES

+

NOTES

+ -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: -

-export TMP=${TMP:-/tmp/SBo} -

-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: -

-export TMP=${TMP:-/home/sbo/tmp} -

-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. -

-Please note that if the CLEANUP variable is set to YES, the TMP setting -is ignored. -

-You can also export variables in sbopkg.conf that are not used by -sbopkg at all. -

  -

ABOUT THE ARCH VARIABLE

+

Overriding Environmental Variables

-You may be wondering why ARCH is not a configuration setting in the -default sbopkg.conf file. The reason is that it does not have to be. If ARCH -is not set, sbopkg does some checking (using 'uname -m') to determine what the -system's architecture is. If the architecture is x86, x86_64, or arm*, then -sbopkg automatically sets ARCH to i486, x86_64, or arm, respectively. If ARCH -is set, sbopkg will inherit that setting. 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 one of the -previously mentioned architectures, then ARCH will be set by whatever is in -the SlackBuild scripts. Note that the SlackBuild may, in certain instances, -discard or override previous ARCH settings if this is required for the build. +It is possible to set or override environmental variables and pass them +to the SlackBuilds when they are built from within +sbopkg. + +This is already demonstrated in the following example line (and others +like it) in the +sbopkg.conf + +file: +

+ +

+export TMP=${TMP:-/tmp/SBo}
+
+ +
+ +

+ +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: +

+

+ +

+export TMP=${TMP:-/home/sbo/tmp}
+
+ +
+ +

+ +would then set +TMP + +to +/home/sbo/tmp + +for building SBo packages and still allow it to be overridden at runtime +by invoking +sbopkg + +as +

+

+ +

+# export TMP=foo; sbopkg
+
+ +
+ +

+ +OUTPUT + +can also be changed to save compiled packages in a location other than +the default of +/tmp. + +

+ +You can also export variables in +sbopkg.conf + +that are not used by +sbopkg + +at all. +   +

About the ARCH Variable

+ +You may be wondering why +ARCH + +is not a configuration setting in the default +sbopkg.conf + +file. +The reason is that it does not have to be. +If +ARCH + +is not set, +sbopkg + +does some checking (using the output of +uname -m) + +to determine what the system's architecture is. +If the architecture is x86, x86_64, or arm*, then +sbopkg + +automatically sets +ARCH + +to i486, x86_64, or arm, respectively. +If +ARCH + +is set, +sbopkg + +will inherit that setting. +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 one of the previously mentioned architectures, then +ARCH + +will be set by whatever is in the SlackBuilds. +Note that the SlackBuild may, in certain instances, discard or override +previous +ARCH + +settings if this is required for the build. + + 

FILES

-/etc/sbopkg/sbopkg.conf +
+
/etc/sbopkg/sbopkg.conf - - File to specify configuration options. -

-/etc/sbopkg/renames.d/50-default +

+File to specify configuration options. +
/etc/sbopkg/renames.d/50-default - - 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. -

-/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo} +

+Default file that lists software in the SBo repository that has been +renamed. +See the +README-renames.d - - Three default files for various types of sbopkg repositories. See the -README-repos.d document in the sbopkg doc/ directory for more information. +document in the +sbopkg + +documentation directory for more information. +
/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo} + +
+Three default files for various types of +sbopkg + +repositories. +See the +README-repos.d + +document in the +sbopkg + +documentation directory for more information. + +
+  +

AUTHORS

+ +Chess Griffin +<chess@chessgriffin.com>

-  + +Mauro Giachero +<mauro.giachero@gmail.com> +

+ +slakmagik +<slakmagik@gmail.com> + + + + 

SEE ALSO

-sbopkg(8) +diff(1), -doc/README +rsync(1), -doc/README-queuefiles +sbopkg(8), -doc/README-renames.d +uname(1), -doc/README-repos.d +wget(1), + +/usr/doc/sbopkg-0.34.0/* -doc/queuefiles/*

@@ -398,15 +763,19 @@ README-repos.d document in the sbopkg doc/ directory for more information.

NAME
DESCRIPTION
-
OVERRIDING ENVIRONMENTAL VARIABLES
-
ABOUT THE ARCH VARIABLE
-
FILES
-
SEE ALSO
+
NOTES
+
+
Overriding Environmental Variables
+
About the ARCH Variable
+
+
FILES
+
AUTHORS
+
SEE ALSO
This document was created by man2html, using the manual pages.
-Time: 18:31:58 GMT, May 27, 2010 +Time: 03:40:11 GMT, November 12, 2010 diff --git a/tools/sbopkg-help b/tools/sbopkg-help index 56310d6..857e5b8 100644 --- a/tools/sbopkg-help +++ b/tools/sbopkg-help @@ -1,4 +1,4 @@ -sbopkg 0.33.1 +sbopkg 0.34.0 Usage: sbopkg [OPTIONS] Options are: -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, 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' diff --git a/tools/sbopkg.SlackBuild b/tools/sbopkg.SlackBuild index 6732612..10dcfdd 100644 --- a/tools/sbopkg.SlackBuild +++ b/tools/sbopkg.SlackBuild @@ -8,7 +8,7 @@ # SlackBuilds.org template. PRGNAM=sbopkg -VERSION=${VERSION:-0.33.1} +VERSION=${VERSION:-0.34.0} ARCH=${ARCH:-noarch} BUILD=${BUILD:-1} TAG=${TAG:-_cng} diff --git a/tools/sbopkg8.html b/tools/sbopkg8.html index d0a9375..160edf9 100644 --- a/tools/sbopkg8.html +++ b/tools/sbopkg8.html @@ -3,359 +3,723 @@ Content-type: text/html Manpage of SBOPKG

SBOPKG

-Section: (8)
Updated: May 2010
Index +Section: (8)
Updated: November 2010
Index Return to Main Contents
+  

NAME

-sbopkg +sbopkg - the SlackBuilds.org package browser - - The SlackBuilds.org Package Browser -

 

SYNOPSIS

sbopkg -[options] +[options] + -

 

DESCRIPTION

-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. -

+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. +   -

INSTRUCTIONS

+

Instructions

-Sbopkg usage assumes an understanding of SlackBuild scripts, -generally, and the third-party repository SlackBuilds.org, -specifically. A thorough reading of http://www.slackbuilds.org/howto/ -and the pages at http://www.slackwiki.org about SlackBuild scripts is -strongly advised. -

-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 -sbopkg.conf +Sbopkg -(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 +http://www.slackbuilds.org/howto/ + +and the pages at +http://www.slackwiki.org + +about SlackBuilds is strongly advised.

-Sbopkg can be run from the command line by simply invoking "sbopkg." -Sbopkg must be run as the root user (since the SlackBuild scripts at -SlackBuilds.org are written with the intention of being run as root). -Furthermore, using 'su -' instead of 'su' is strongly encouraged. -The reason is that some SlackBuild scripts rely on certain tools that -are only available in root's $PATH when root's $PATH is inherited -(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 -line 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 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. + +In order for +sbopkg + +to be used, a configuration file must exist at +/etc/sbopkg/sbopkg.conf. + +An initial install will provide the user with that file while upgrades +will add an +/etc/sbopkg/sbopkg.conf.new + +which may be merged with or replace the older version. +See +sbopkg.conf(5) + +for more information about the configuration file.

-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. + +Sbopkg + +must be run as the root user (since the SBo SlackBuilds are written with +the intention of being run as root). +Furthermore, using the +- + +option with +su + +is strongly encouraged. +The reason is that some SlackBuilds rely on certain tools that are only +available in root's +PATH + +when the scripts in +/etc/profile.d + +have been run (i.e., +texmf + +to build man pages), which is only done for login shells, or otherwise +require a ``truer'' root environment than that given by only +su. + +In any event, invoking +sbopkg + +with no arguments (or with just +-d, + +-f, + +or +-V) + +will launch the +dialog-based + +interface, and the menus provided should be fairly self-explanatory.

-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. + +The main menu allows the user to synchronize with the SBo repository. +This is the first step to take (after configuration) with a new install +of +sbopkg. + +Currently, the size of a local copy of the SBo repository is about +about 90MB. +The main menu also allows the user to view the SBo +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 a sync. +Additionally, the user can choose to build a package 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 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 +KEEPLOG + +is set to +YES + +in the +sbopkg.conf + +file then a permanent log of the build process is saved. +See +sbopkg.conf(5) + +under +KEEPLOG + +and +LOGFILE + +for details.

-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. + +Alternatively, +sbopkg + +can be run from the command line without using the +dialog + +interface. +See the +OPTIONS + +section for the available command line options.

+ +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 an ``@''. +See the +readme-queuefiles + +document in the documentation directory for more information. +

+ +Certain features of +sbopkg + +rely on outside binaries, such as a pager to view the text files when +sbopkg + +is run from the command line, and an editor to edit the +.info + +or +SlackBuild + +files. +The paging functions will look to the environmental variable +PAGER + +and, if that variable is not defined, it will default to +more. + +Similarly, the editing functions will look to +EDITOR + +and will default to +vi. + +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. +  

OPTIONS

+
-
-b PACKAGE(s)/QUEUE(s) +
-b PACKAGE(s)/QUEUE(s)
-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: -

-#sbopkg -b "foo bar" -

-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. -

+Build packages of the argument(s) from the active repository. +If more than one package is specified, they may either be quoted or the +switch can be given multiple times. +Using this second form, a colon-separated list of options may be given. +If whitespace occurs between the colons, it must be quoted. +

+For example: +
+
+
+
+# sbopkg -b "foo bar"
+
+ +
+
+ +
+will build +foo + +and then +bar. + +
+Or +
+
+
+
+# sbopkg -b app1:opt1="foo bar":opt2=baz -b app2:opt=mu
+
+ +
+
+ +
+will build app1 with the options ``foo bar'' and ``baz'', and app2 with +the option ``mu''. +
+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. +A way to avoid this is to specify the queuefile with its +.sqf + +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. +
-c
-Display list of installed SBo packages and potential updates. -

-

-d DIRECTORY +Display a list of installed SBo packages and potential updates. + +
-d DIRECTORY
-Manually specify the full path to the DIRECTORY containing the -local SBo repository. -

-

-e ask|continue|stop +Manually specify the full path to the +DIRECTORY + +containing the local SBo repository. + +
-e ask|continue|stop
-Specify what sbopkg should do when it encounters an error while building a -package. Valid options are: -

-ask +Specify what +sbopkg -: This is the default behavior, asking the user what to do; -

-continue +should do when it encounters an error while building a package. +Valid options are: +

+ask: -: Ignore the error and continue processing (act as if the user -answered "Yes" to all questions); -

-stop +This is the default behavior, asking the user what to do. +

+continue: -: Stop the processing (act as if the user answered "No" to all -questions). -

-

-f +Ignore the error and continue processing (act as if the user answered +``Yes'' to all questions). +
+stop: + +Stop the processing (act as if the user answered ``No'' to all questions). + +
-f FILE
-Override the default configuration file, which is located by -default at /etc/sbopkg/sbopkg.conf, with another configuration -file. -

-

-g PACKAGE(s) +Override the default configuration file, +/etc/sbopkg/sbopkg.conf, + +with +FILE. + + +
-g PACKAGE(s)
-General search for PACKAGE(s) by glob. For example: -

-#sbopkg -g nv -

-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. -

+General search for +PACKAGE(s) + +by case-insensitive glob where the argument is automatically wrapped in +*s. + +If more than one glob is specified, they must be quoted or the -g flag +must be used multiple times, once for each glob. +

+For example: +
+
+
+
+# sbopkg -g "foo bar"
+
+ +
+
+ +
+will return a list of packages with either +foo + +or +bar + +in their names. +
-h
Display the help. -

-

-i PACKAGE(s) + +
-i PACKAGE(s)/QUEUE(s)
-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: -

-#sbopkg -i "foo bar" -

-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. -

-Queuefile names are supported, too. See the explanation for the '-b' -command for details. -

+Build and install packages of the argument(s) from the active +repository. +

+See the +-b + +option for details since, other than the installation, these two options +operate similarly. +
+Note that 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 it works, it can be helpful. +
-k
-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. -

+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. +

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. -

+option is specified +sbopkg + +will also omit the build of different versions of installed packages. +

-l
-Display the SBo ChangeLog.txt and quit. -

+Display the SBo +ChangeLog + +and quit. +

-o
-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. -

-Source files are obsolete when no SBo script references it any more, -which is something that can happen after rsync-ing the local -repository. -

-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. -

+

+Source files are obsolete when no +.info + +file's +DOWNLOAD + +field(s) reference it any more, which is something that can happen after +syncing the local repository. +
+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. +
-P
List the cached package files which are not currently installed on the system and optionally delete them. -

+

-p
-List installed SlackBuilds.org packages. -

+List installed SBo packages. +

-q
-Enable the "quiet mode." When this flag is specified, the output of -some of the command-line options is minimized. -

-

-r +Enable the ``quiet mode.'' +When this flag is specified, the output of some of the command-line +options is minimized. -
-Rsync the local repository with SlackBuilds.org and quit. -

-R
-Show all the README files of the queued packages before starting the build. -This is useful when you want to make a final check. -

-

-s PACKAGE(s) +Show all the +README + +files of the queued packages before starting the build. +This is useful when the user wants to make a final check. + +
-r
-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: -

-#sbopkg -s "foo bar" -

-will search for foo and then bar. -

+``Rsync'' the local repository with SBo and quit. + +

-s PACKAGE(s) + +
+Specific search for +PACKAGE(s) + +by case-sensitive glob and, if found, display the +README, + +SlackBuild, + +.info, + +and +slack-desc + +files in that order for each +PACKAGE + +found, using +$PAGER. + +If more than one glob is specified, they must be quoted or the -s flag +must be used multiple times, once for each glob. +
+For example: +
+
+
+
+# sbopkg -s "foo bar"
+
+ +
+
+ +
+will display all the above-mentioned files for packages whose names are +exactly +foo + +or +bar. + +
+Note that shell metacharacters may be supplied in the arguments. For +instance, +
+
+
+
+# sbopkg -s '*[Oo]pen*'
+
+ +
+
+ +
+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. +
-u
-Check for an update to sbopkg itself and then quit. -

-

-V REPO/BRANCH +Check for an update to +sbopkg + +itself and then quit. + +
-V VERSION
Set the repository and branch to use. -

-For a list of valid versions, invoke sbopkg as -sbopkg -V ?. +

+For a list of valid versions, invoke +sbopkg +as +
+
+
+
+# sbopkg -V ?
+
+ +
+
+ +
See the -sbopkg.conf (5) +sbopkg.conf(5) + +man page for more information about the ``local'' repository. +
+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. -man page for more information about the 'local' repository. -

-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. -

-v
-Prints the current version of sbopkg on stdout. -

+Prints the current version of +sbopkg + +on stdout. +

 

FILES

-/etc/sbopkg/sbopkg.conf +
+
/etc/sbopkg/sbopkg.conf - - File to specify configuration options. -

-/etc/sbopkg/renames.d/50-default +

+Default system-wide file to specify configuration options. +
/etc/sbopkg/renames.d/50-default - - 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. -

-/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo} +

+Default file that lists software in the SBo repositories that has been +renamed. +See the +README-renames.d - - Three default files for various types of sbopkg repositories. See the -README-repos.d document in the sbopkg doc/ directory for more information. -

+document in the +sbopkg + +documentation directory for more information. +

/etc/sbopkg/repos.d/{40-sbo.repo,50-sb64.repo,60-local.repo} + +
+Three default files for various types of +sbopkg + +repositories. +See the +README-repos.d + +document in the +sbopkg + +documentation directory for more information. + +
  -

SEE ALSO

- -sbopkg.conf(5) - -doc/README - -doc/README-queuefiles - -doc/README-renames.d - -doc/README-repos.d - -doc/queuefiles/* - -

-  -

AUTHOR

+

AUTHORS

Chess Griffin <chess@chessgriffin.com>

+Mauro Giachero +<mauro.giachero@gmail.com> +

+ +slakmagik +<slakmagik@gmail.com> + + + +  +

SEE ALSO

+ +dialog(1), + +more(1), + +removepkg(8), + +rsync(1), + +sbopkg.conf(5), + +su(1), + +upgradepkg(8), + +vi(1), + +/usr/doc/sbopkg-0.34.0/* + + +

+

 

Index

NAME
SYNOPSIS
DESCRIPTION
-
INSTRUCTIONS
+
+
Instructions
+
OPTIONS
FILES
-
SEE ALSO
-
AUTHOR
+
AUTHORS
+
SEE ALSO
This document was created by man2html, using the manual pages.
-Time: 18:31:58 GMT, May 27, 2010 +Time: 03:40:11 GMT, November 12, 2010