[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
wiki:user:mfillpot:sbopkg [2012/09/01 19:25 (UTC)] – added "no edit" note mfillpotwiki:user:mfillpot:sbopkg [2012/12/20 04:14 (UTC)] (current) – [Application CLI Use] added content mfillpot
Line 49: Line 49:
   * **50-local.repo** - This file can point to a custom repo such as a centralized repo for a corporation or other organization   * **50-local.repo** - This file can point to a custom repo such as a centralized repo for a corporation or other organization
   * **60-SBo-current.repo** - This is another custom repo file which by default is pointing to ponce's slackware-current script repo.   * **60-SBo-current.repo** - This is another custom repo file which by default is pointing to ponce's slackware-current script repo.
-  * **70-sb64.repo** - This file creates a repo option for the Slamd64 distribution's build script repo 
  
 ====Using the Rename Option==== ====Using the Rename Option====
Line 56: Line 55:
 All files in the renames.d will be replaced as the sbopkg application is updated, if you make changes to any of the file you will need to backup your changes in another location so they can be reverted.</note>  All files in the renames.d will be replaced as the sbopkg application is updated, if you make changes to any of the file you will need to backup your changes in another location so they can be reverted.</note> 
  
-<note warning>Current Working Point</note>+Sometimes it may be necessary to rename the SlackBuild archive for an application to avoid naming conflicts and simplify the organization of the packages in sbopkg. If you wish to apply alternate names to known SlackBuilds you will should first create a new file in the **/etc/sbopkg/renames.d/** directory that follows the debian style naming of {number}-{name}.renames, I recommend a simple name like 70-custom.renames so the default file takes precedence.
  
-===== Queue Files =====+The file contents are very simple, OldName=NewName. 
 +An example would be to rename the i3 window manager SlackBuild to i3wm so it is better reflected as a window manager. 
 +Create a new file named **/etc/sbopkg/renames.d/70-custom.renames**, open the file in your favorite text editor and add the following: 
 +<code># oldname=newname 
 +i3=i3wm</code> 
  
 +As you can see the comment was added to make future modifications easier and the syntax is also very simple to understand.
 ===== Application Use ===== ===== Application Use =====
-==== Application GUI Use ====+ 
 +The sbopkg application has two possible modes, CLI and GUI. Both have pros and cons, as with any tool, the user should utilize the balance of tools that best fit their needs. 
 ==== Application CLI Use ==== ==== Application CLI Use ====
 +<note> **The listed options may be out-of-date** \\ Refer to the command ''sbopkg -h'' to confirm which options are available in your installed version.</note>
 +
 +The most basic and functional use of the **sbopkg** utility is through the command line, the only real limitation is lacking the ability to generate queu files.
 +
 +=== First Use ===
 +After the application is installed, your first task is to create the necessary files and pull a copy of the active SlabkBuilds.org repo.
 +
 +To accomplish all of the listed tasks you simply need to issue the command to sync the repo.
 +<code>root@darkstar#sbopkg -r</code>
 +//This will also create the necessary directories to hold the repo, cache, queue files and output packages.//
 +
 +Upon completion of the syncronization procedure you are free to build, install or inspect all slackbuild from http://www.SlackBuilds.org which have been downloaded into your local filesystem.
 +
 +=== General Use ===
 +
 +**Basic Commands**
 +  * **-u** - check for an update to sbopkg.
 +  * **-r** - Sync the local repo
 +  * **-c** - check for updates to installed SBo packages
 +  * **-d** - Download the source archive for the selected application(s).
 +  * **-b** - Download the source and build packages for the selected application(s).
 +  * **-i** - Download the source, build packages and install/upgrade packages for the selected application(s).
 +  * **-k** - skip selected process for installed application(s)
 +
 +**Search and Display Options**
 +  * **-R** - Display the README for the selected application.
 +  * **-g** - Search for package name that matches a string.
 +  * **-s** - Search for a specific package and display the package information.
 +
 +**Cache and File Maintenance**
 +  * **-o** - Display the obsolete source files and prompt for deletion.
 +  * **-P** - Display the cache files for uninstalled apps and prompt for deletion.
 +
 +=== Building Applications from the SlackBuilds.org Repo ===
 +Before each set of uses it is recommended to re-sync the repo to guarantee that all updated and new SlackBuilds are available, this is again accomplished with the **-r** option.
 +
 +For this example we will conduct all steps necessary to install the pysolfc application. As the goal is to download the source, build and install this application, you will use the **-i** option as shown below.
 +<code>root@darkstar#sbopkg -i pysolfc</code>
 +Upon submitting the command all steps will begin running and the application will display the verbose output, you will also be prompted if there is an error or the checksum does not match the file.
 +
 +<note>If you wish to install more than one application you will include all requested applications in package name argurment within a single set of quotes, for example "pysolfc qrencode".</note>
 +
 +=== Updating Installed Applications/Libraries ===
 +To search for updates to applications and libraries that were installed from SlackBuilds you must first re-sync your repo to gather all updates. Upon completing that task you will issue the **-c** option, after a quick scan the list of potential updates will be displayed.
 +
 +<code>
 +root@darkstar# sbopkg -c
 +[ Checking for potential updates ]
 +This may take a few moments. Press <ESC> to abort.
 +100%[======================================================================]
 +Listing installed SBo repository for Slackware 14.0 packages and flagging
 +potential updates...
 +
 +google-talkplugin:
 +  INSTALLED PACKAGE IS NEWER THAN REPO
 +  Installed version:  google-talkplugin-3.10.2.0-i386-1_SBo
 +  Repo version:  google-talkplugin-2.6.1.0-i486-1_SBo
 +  Note: repo version not obtainable by standard method, may be inaccurate.
 +libevent:
 +  POTENTIAL UPDATE
 +  Installed version:  libevent-2.0.10-i486-1_SBo
 +  Repo version:  libevent-2.0.21-i486-1_SBo
 +mathomatic:
 +  INSTALLED PACKAGE IS NEWER THAN REPO
 +  Installed version:  mathomatic-16.0.5-i486-1_SBo
 +  Repo version:  mathomatic-15.8.5-i486-1_SBo
 +warzone2100:
 +  INSTALLED PACKAGE IS NEWER THAN REPO
 +  Installed version:  warzone2100-3.1_rc3-i486-1_SBo
 +  Repo version:  warzone2100-2.3.8-i486-1_SBo
 +
 +Potential update list complete.
 +</code>
 + 
 +You can then install build and install the newly updated applications with the standard install and build options.
 +
 +<note warning>Current Working Point</note>
 +==== Application GUI Use ====
 +
 +===== Queue Files =====
  
 ===== Making Sbopkg Handle Dependencies ===== ===== Making Sbopkg Handle Dependencies =====
Line 172: Line 258:
 <!-- Please do not modify anything below, except adding new tags.--> <!-- Please do not modify anything below, except adding new tags.-->
 <!-- You must also remove the tag-word "template" below. Otherwise your page will not show up in the Table of Contents --> <!-- You must also remove the tag-word "template" below. Otherwise your page will not show up in the Table of Contents -->
-{{tag>work_in_progress }}+{{tag>author_mfillpot work_in_progress }}
 wiki:user:mfillpot:sbopkg ()