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

update TODO, README, and sbopkg(8) man page to reflect ability to edit .info file.

Browse source
This commit is contained in:
chess.griffin 2008-10-02 21:45:34 +00:00
parent ce4f27dc05
commit db87665616
3 changed files with 27 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
src/usr/doc/README
View file

@ -14,13 +14,14 @@ user to create, synchronize, search, and browse a local copy of the
SBo repository, read the ChangeLog, list the installed SBo packages, SBo repository, read the ChangeLog, list the installed SBo packages,
display potential updates to SlackBuilds.org packages, view the display potential updates to SlackBuilds.org packages, view the
README, SlackBuild, .info, and slack-desc files for each package, and README, SlackBuild, .info, and slack-desc files for each package, and
make manual edits to a copy of the original SlackBuild. Sbopkg will make manual edits to a copy of the original .info or SlackBuild files.
also allow the user to select packages to build and it will download Sbopkg will also allow the user to select packages to build and it
the source code, check the md5sum, build a Slackware package, and, if will download the source code, check the md5sum, build a Slackware
using the dialog interface, install the package. It will not check package, and, if using the dialog interface, install the package. It
dependencies since that is not a feature native to Slackware. Sbopkg will not check dependencies since that is not a feature native to
is one thing and one thing only: a medium to easily browse a local Slackware. Sbopkg is one thing and one thing only: a medium to easily
copy of the SlackBuilds.org repository and build packages from it. browse a local copy of the SlackBuilds.org repository and build
packages from it.
Sbopkg can be also be used strictly from the command line without the Sbopkg can be also be used strictly from the command line without the
dialog interface to do most of the above items. Typing sbopkg -h dialog interface to do most of the above items. Typing sbopkg -h

2
src/usr/doc/TODO
View file

@ -7,7 +7,7 @@ Sbopkg TODO (in no particular order)
the current -b switch. the current -b switch.
* Add in ability to edit the *.info file so folks can quickly change * Add in ability to edit the *.info file so folks can quickly change
the version or download link (though they'd also have to change the the version or download link (though they'd also have to change the
MD5SUM). MD5SUM). UPDATE: this is now part of sbopkg 0.12.0.
* Perhaps make the MD5SUM check a variable that a user can turn off? * Perhaps make the MD5SUM check a variable that a user can turn off?
* When using the dialog interface, change the listing of packages to * When using the dialog interface, change the listing of packages to
be a checklist or radiolist whereby the user can select more than be a checklist or radiolist whereby the user can select more than

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

@ -32,16 +32,16 @@ view. After choosing a category, the user can then view the various
software packages available in that category within the local SBo software packages available in that category within the local SBo
repository. Selecting a package will display another menu allowing repository. Selecting a package will display another menu allowing
the user to view the package's README, SlackBuild, .info, or the user to view the package's README, SlackBuild, .info, or
slack-desc files. The user can also edit the SlackBuild and the slack-desc files. The user can also edit the .info file and
edited SlackBuild will remain after doing an rsync. Additionally, if SlackBuild and the edited files will remain after doing an rsync.
sbopkg is run with root privileges, then the user can choose to build Additionally, if sbopkg is run with root privileges, then the user can
a package as well using either the original SlackBuild or the choose to build a package as well using either the original SlackBuild
locally-edited one, if present. If using the dialog interface, and if or the locally-edited one, if present. If using the dialog interface,
sbopkg finds a built package for a particular piece of software in the and if sbopkg finds a built package for a particular piece of software
OUTPUT directory, then sbopkg will automatically add a new menu entry in the OUTPUT directory, then sbopkg will automatically add a new menu
allowing the user to install the package if he so choosed. Finally, entry allowing the user to install the package if he so choosed.
if KEEPLOG is set to YES in the sbopkg.conf file then a permanent log Finally, if KEEPLOG is set to YES in the sbopkg.conf file then a
of the build process is saved in /tmp/sbopkg-build-log. permanent log of the build process is saved in /tmp/sbopkg-build-log.
Alternatively, sbopkg can be run from the command line without using Alternatively, sbopkg can be run from the command line without using
the dialog interface. Executing "sbopkg -h" will display a list of the dialog interface. Executing "sbopkg -h" will display a list of
@ -49,14 +49,14 @@ options available from the command line.
Certain features of sbopkg rely on outside binaries, such as a pager 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 to view the text files when sbopkg is run from the comamnd line, and
an editor to edit the SlackBuild. The pager function will look to the an editor to edit the .info or SlackBuild files. The pager function
environmental variable $PAGER and if that variable is not defined then will look to the environmental variable $PAGER and if that variable is
it will default to 'more.' Similarly, the edit SlackBuild function not defined then it will default to 'more.' Similarly, the edit
found when sbopkg is used with the dialog interface will look to function found when sbopkg is used with the dialog interface will look
$EDITOR and will default to 'vi' if no $EDITOR has been defined. If to $EDITOR and will default to 'vi' if no $EDITOR has been defined.
the user wants sbopkg to use another EDITOR, such as nano, then adding If the user wants sbopkg to use another $EDITOR, such as nano, then
the requisite information in ~/.bashrc or other similar configuration adding the requisite information in ~/.bashrc, /etc/profile, or other
file to export EDITOR will suffice. similar configuration file to export $EDITOR will suffice.
.SH OPTIONS .SH OPTIONS
.TP 5 .TP 5