Miroirs/sbopkg
1
0
Fork 0
mirror of https://github.com/sbopkg/sbopkg synced 2024-12-28 09:58:58 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

slight tweaks to prior commit

Browse source
This commit is contained in:
chess.griffin 2010-05-12 20:59:54 +00:00
parent 79adfa16a7
commit bf1ed1fd82
1 changed files with 18 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

35
src/usr/man/man8/sbopkg.8
View file

@ -26,26 +26,27 @@ Before sbopkg can be used, a configuration file must be created at
(5) for more information about the configuration file. (5) for more information about the configuration file.
Sbopkg can be run from the command line by simply invoking "sbopkg." 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). SlackBuilds.org are written with the intention of being run as root).
Furthermore, using 'su -' instead of 'su' is strongly encouraged. Furthermore, using 'su -' instead of 'su' is strongly encouraged.
The reason is that some SlackBuild scripts rely on certain tools that 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 are only available in root's $PATH when root's $PATH is inherited
root's $PATH is not inherited when only using 'su'. In any evnet, (i.e. texmf to build man pages) and root's $PATH is not inherited when
invoking 'sbopkg' from the command line will launch the dialog-based only using 'su'. In any evnet, invoking 'sbopkg' from the command
interface, and the menus provided should be fairly self-explanatory. line will launch the dialog-based interface, and the menus provided
The main menu allows the user to rsync with the SlackBuilds.org should be fairly self-explanatory. The main menu allows the user to
repository (currently, the size of a local copy of the SBo repository rsync with the SlackBuilds.org repository (currently, the size of a
is less than 50MB), view the SlackBuilds.org Changelog, check for local copy of the SBo repository is less than 50MB), view the
potential updates to SBo packages, display the contents of the local SlackBuilds.org Changelog, check for potential updates to SBo
cache directory where source tarballs are saved, display the permanent packages, display the contents of the local cache directory where
build log, and browse or search the local copy of the SBo repository. source tarballs are saved, display the permanent build log, and browse
Once the browse function is chosen, the user can select the category or search the local copy of the SBo repository. Once the browse
of software to view. After choosing a category, the user can then function is chosen, the user can select the category of software to
view the various software packages available in that category within view. After choosing a category, the user can then view the various
the local SBo repository. Selecting a package will display another software packages available in that category within the local SBo
menu allowing the user to view the package's README, SlackBuild, repository. Selecting a package will display another menu allowing
.info, or slack-desc files. The user can also edit the .info file and 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. SlackBuild and the edited files will remain after doing an rsync.
Additionally, the user can choose to build a package as well using Additionally, the user can choose to build a package as well using
either the original SlackBuild or the locally-edited one, if present. either the original SlackBuild or the locally-edited one, if present.