From fa840ab13bac999f54276e9a234d20f5d1b6266b Mon Sep 17 00:00:00 2001 From: "chess.griffin" Date: Mon, 29 Dec 2008 04:38:35 +0000 Subject: [PATCH] mention in README and both man pages that local copy of SBo repo is less than 50MB. --- src/usr/doc/README | 27 ++++++++++++++------------- src/usr/man/man5/sbopkg.conf.5 | 3 ++- src/usr/man/man8/sbopkg.8 | 3 ++- 3 files changed, 18 insertions(+), 15 deletions(-) diff --git a/src/usr/doc/README b/src/usr/doc/README index c84c584..997743d 100644 --- a/src/usr/doc/README +++ b/src/usr/doc/README @@ -11,19 +11,20 @@ Sbopkg is a command-line and dialog-based tool to synchronize with the SlackBuilds.org ("SBo") repository, a collection of third-party SlackBuild scripts to build Slackware packages. Sbopkg will allow the user to create, synchronize, search, and browse a local copy of the -SBo repository, read the ChangeLog, list the installed SBo packages, -display potential updates to SlackBuilds.org packages, view the -README, SlackBuild, .info, and slack-desc files for each package, and -make manual edits to a copy of the original .info or SlackBuild files. -Sbopkg will also allow the user to select packages to build and it -will download the source code, check the md5sum, build a Slackware -package, and, optionally install the package. The user can also -build, and optionally install, more than one package by using the -'build queue' feature. Sbopkg will not check dependencies since that -is not a feature native to Slackware, but since the build queue will -process packages in the order listed, it sometimes may be possible to -build and install dependencies in order prior to building and -installing the final, desired package. Ultimately, Sbopkg is one +SBo repository (currently, the size of a local copy of the SBo +repository is less than 50MB), read the ChangeLog, list the installed +SBo packages, display potential updates to SlackBuilds.org packages, +view the README, SlackBuild, .info, and slack-desc files for each +package, and make manual edits to a copy of the original .info or +SlackBuild files. Sbopkg will also allow the user to select packages +to build and it will download the source code, check the md5sum, build +a Slackware package, and, optionally install the package. The user +can also build, and optionally install, more than one package by using +the 'build queue' feature. Sbopkg will not check dependencies since +that is not a feature native to Slackware, but since the build queue +will process packages in the order listed, it sometimes may be +possible to build and install dependencies in order prior to building +and installing the final, desired package. Ultimately, Sbopkg is one thing and one thing only: a medium to easily browse a local copy of the SlackBuilds.org repository and build packages from it. diff --git a/src/usr/man/man5/sbopkg.conf.5 b/src/usr/man/man5/sbopkg.conf.5 index c1fd41a..a041253 100644 --- a/src/usr/man/man5/sbopkg.conf.5 +++ b/src/usr/man/man5/sbopkg.conf.5 @@ -34,7 +34,8 @@ The default value of SLACKVER is: 12.2. .B LOCALREPO .br This option allows the user to set the location of the local rsync -mirror of the SBo repository. +mirror of the SBo repository. Currently, the size of a local copy of +the SBo repository is less than 50MB. The default value of LOCALREPO is: .br diff --git a/src/usr/man/man8/sbopkg.8 b/src/usr/man/man8/sbopkg.8 index 83fb170..5e185dc 100644 --- a/src/usr/man/man8/sbopkg.8 +++ b/src/usr/man/man8/sbopkg.8 @@ -22,7 +22,8 @@ Before sbopkg can be used, a configuration file must be created at Sbopkg can be run from the command line by simply invoking "sbopkg." Doing so will launch the dialog-based interface, and the menus provided should be fairly self-explanatory. The main menu allows the -user to rsync with the SlackBuilds.org repository, view 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