From bf1ed1fd82b94660481a4f9ca054d45fda24d2a7 Mon Sep 17 00:00:00 2001 From: "chess.griffin" Date: Wed, 12 May 2010 20:59:54 +0000 Subject: [PATCH] slight tweaks to prior commit --- src/usr/man/man8/sbopkg.8 | 35 ++++++++++++++++++----------------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/src/usr/man/man8/sbopkg.8 b/src/usr/man/man8/sbopkg.8 index 370cb61..bbb7e72 100644 --- a/src/usr/man/man8/sbopkg.8 +++ b/src/usr/man/man8/sbopkg.8 @@ -26,26 +26,27 @@ Before sbopkg can be used, a configuration file must be created at (5) for more information about the configuration file. Sbopkg can be run from the command line by simply invoking "sbopkg." -Sbopkg must be run as the root user (since the SlackBuild scrips at +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 (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 +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.