SlackBuilds package tool
Go to file
Erich Ritz 371284cd89
sbopkg: Use correct SlackBuild file name to build package
During package creation, most SlackBuilds copy the .SlackBuild file to
/usr/doc/$PKG/.  Previously, sbopkg would cause the "original"
SlackBuild instead of the "local" SlackBuild with user edits to be
copied to the documentation directory.  Now, sbopkg backs up the
original SlackBuild to $PKGNAME.SlackBuild.original before building the
package.

Old behavior:
1. Original (upstream) SlackBuild is named $PKGNAME.SlackBuild.
2. User optionally defines custom SlackBuild in
   $PKGNAME.SlackBuild.sbopkg.
3. sbopkg asks user to use Original or Local SlackBuild, and copies
   $PKGNAME.SlackBuild or $PKGNAME.SlackBuild.sbopkg to
   $PKGNAME.SlackBuild.build, respectively.
4. sbopkg builds package (which includes copying SlackBuild to
   /usr/doc/).
5. sbopkg removes *.build files.

New behavior:
1. Original (upstream) SlackBuild is named $PKGNAME.SlackBuild.
2. User optionally defines custom SlackBuild in
   $PKGNAME.SlackBuild.sbopkg.
3. sbopkg asks user to use Original or Local SlackBuild, and copies
   $PKGNAME.SlackBuild or $PKGNAME.SlackBuild.sbopkg to
   $PKGNAME.SlackBuild.build, respectively.
4. sbopkg backs up original SlackBuild by moving $PKGNAME.SlackBuild
   to $PKGNAME.SlackBuild.original.
5. sbopkg copies $PKGNAME.SlackBuild.build to $PKGNAME.SlackBuild.
6. sbopkg builds package (which includes copying SlackBuild to
   /usr/doc/).
7. sbopkg restores original SlackBuild by moving
   $PKGNAME.SlackBuild.original to $PKGNAME.SlackBuild.
8. sbopkg removes *.build files.

Signed-off-by: Willy Sudiarto Raharjo <willysr@sbopkg.org>
2018-01-12 07:53:02 +07:00
src sbopkg: Use correct SlackBuild file name to build package 2018-01-12 07:53:02 +07:00
tools sbopkg: Use correct SlackBuild file name to build package 2018-01-12 07:53:02 +07:00
LICENSE.md sbopkg: Update copyright to 2018. 2018-01-01 22:03:47 +07:00
README.md README: Update text. 2017-06-18 09:34:05 +07:00

sbopkg

Slackbuilds.org Package Browser

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 is actively maintained and a new version is released one or more times per Slackware/SBo release. Numerous people have contributed diffs, bug reports, and helpful suggestions and they are all mentioned in the THANKS file in /usr/doc/sbopkg-$VERSION. This utility would not be anywhere close to its present state without the help of these folks.

Features

Sbopkg will allow the user to:

  • Create, browse, and search a local copy of the SBo repository for any supported Slackware version.
  • Read the SBo ChangeLog.txt.
  • Display a list of all SBo packages installed on the user's system.
  • Display potential updates to packages installed from SlackBuilds.org.
  • View the README, SlackBuild, .info, and slack-desc files for each individual piece of software in the repository.
  • Copy the original .info file or SlackBuild for editing.
  • Automatically download the source code, check the md5sum, and build or build and install a Slackware package from either the original .info file and SlackBuild or the locally-edited copies.
  • Batch queue packages for building or building and installing.
  • Load, save, and use sbopkg queuefiles (.sqf), several of which are included with the package.
  • View the contents of the cache directory (where source code tarballs are stored).
  • View the permanent build log that is optionally maintained to keep a record of the entire compilation process.
  • Check for an update to sbopkg itself.

Sbopkg will not check dependencies since that is not a feature native to Slackware. 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. However, since 0.38.0, sqg (SBo Queue Generator) is included in the main package, so users can easily generate queue file(s) which list all dependencies and install them along the requested package.

Sbopkg can be also be used strictly from the command line without the dialog interface, to perform most, if not all, of the same functions listed above. Typing sbopkg -h will display the command line options.

Please note that while sbopkg has performed well for many users, it is still advised to read the ChangeLog and READMEs before building package(s).