tag and release version 0.33.0

This commit is contained in:
slakmagik 2010-05-24 22:32:33 +00:00
parent 9bb1e4a140
commit 1045ba463e
10 changed files with 92 additions and 70 deletions

View File

@ -1,30 +1,6 @@
Fri Mar 5 21:46:41 UTC 2010
Mon May 24 20:53:43 UTC 2010
Sbopkg 0.XX.X 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.
*
+--------------------------+

View File

@ -1,3 +1,33 @@
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.
+--------------------------+
Fri Mar 5 21:29:21 UTC 2010
Sbopkg 0.32.0 released. This version contains the following fixes and
enhancements:

View File

@ -1 +1 @@
http://sbopkg.googlecode.com/files/sbopkg-0.32.0-noarch-1_cng.tgz
http://sbopkg.googlecode.com/files/sbopkg-0.33.0-noarch-1_cng.tgz

View File

@ -1 +1 @@
sbopkg-0.32.0-noarch-1_cng.tgz
sbopkg-0.33.0-noarch-1_cng.tgz

View File

@ -1 +1 @@
sbopkg-0.32.0.tar.gz
sbopkg-0.33.0.tar.gz

View File

@ -1 +1 @@
0.32.0
0.33.0

View File

@ -3,7 +3,7 @@ Content-type: text/html
<HTML><HEAD><TITLE>Manpage of SBOPKG.CONF</TITLE>
</HEAD><BODY>
<H1>SBOPKG.CONF</H1>
Section: (5)<BR>Updated: February 2010<BR><A HREF="#index">Index</A>
Section: (5)<BR>Updated: May 2010<BR><A HREF="#index">Index</A>
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
<A NAME="lbAB">&nbsp;</A>
@ -55,14 +55,14 @@ REPO_NAME=${REPO_NAME:-SBo}.
<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.
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.
<P>
The default value of REPO_BRANCH is:
<BR>
REPO_BRANCH=${REPO_BRANCH:-13.0}.
REPO_BRANCH=${REPO_BRANCH:-13.1}.
<P>
<DT><B>REPO_ROOT</B>
@ -286,7 +286,7 @@ these default options is not recommended.
The default value of WGETFLAGS is:
<BR>
&quot;--continue --progress-bar --timeout=15 --tries=5&quot;.
&quot;--continue --progress-bar:force --timeout=15 --tries=5&quot;.
<P>
<DT><B>DIFF</B>
@ -406,6 +406,6 @@ README-repos.d document in the sbopkg doc/ directory for more information.
This document was created by
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR>
Time: 21:44:48 GMT, March 05, 2010
Time: 20:55:24 GMT, May 24, 2010
</BODY>
</HTML>

View File

@ -1,4 +1,4 @@
sbopkg 0.32.0
sbopkg 0.33.0
Usage: sbopkg [OPTIONS] <packagename(s)>
Options are:
-b pkg/queue(s) Build the specified package(s). If one or more queuefiles
@ -13,8 +13,9 @@ Options are:
-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.
-o Display the obsolete source files & prompt for deletion.
-P List uninstalled cached package files & prompt for deletion.
-p List installed packages from active repo.
-q Quiet some of the command-line output.
-r Sync the remote repository with the local mirror and then
quit.
@ -22,13 +23,10 @@ Options are:
-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).
-v Print sbopkg's version on stdout.
-V repo/branch Set the repository/branch. The repo is optional and, if
not given, sbopkg will try to make the best match,
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")

View File

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

View File

@ -3,7 +3,7 @@ Content-type: text/html
<HTML><HEAD><TITLE>Manpage of SBOPKG</TITLE>
</HEAD><BODY>
<H1>SBOPKG</H1>
Section: (8)<BR>Updated: October 2009<BR><A HREF="#index">Index</A>
Section: (8)<BR>Updated: May 2010<BR><A HREF="#index">Index</A>
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>
<A NAME="lbAB">&nbsp;</A>
@ -45,10 +45,17 @@ Before sbopkg can be used, a configuration file must be created at
(5) for more information about the configuration file.
<P>
Sbopkg can be run from the command line by simply invoking &quot;sbopkg.&quot;
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
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
@ -60,16 +67,16 @@ 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.
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>
Alternatively, sbopkg can be run from the command line without using
the dialog interface. Executing &quot;sbopkg -h&quot; will display a list of
@ -223,6 +230,12 @@ 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 &quot;other&quot; repository will be listed.
<P>
<DT><B>-P</B>
<DD>
List the cached package files which are not currently installed on the
system and optionally delete them.
<P>
<DT><B>-p</B>
<DD>
@ -262,24 +275,29 @@ will search for foo and then bar.
<DD>
Check for an update to sbopkg itself and then quit.
<P>
<DT><B>-v VERSION</B>
<DT><B>-V REPO/BRANCH</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.
For a list of valid versions, invoke sbopkg as
<B>sbopkg -V ?</B>.
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
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>
<DD>
Prints the current version of sbopkg on stdout.
<P>
</DL>
<A NAME="lbAG">&nbsp;</A>
<H2>FILES</H2>
@ -338,6 +356,6 @@ Chess Griffin
This document was created by
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR>
Time: 21:44:48 GMT, March 05, 2010
Time: 20:55:24 GMT, May 24, 2010
</BODY>
</HTML>