[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
Next revisionBoth sides next revision
wiki:user:mfillpot:sbopkg [2012/10/11 01:16 (UTC)] – [Selecting Repos (Optional)] slamd64 repo removed as project is obsolete mfillpotwiki:user:mfillpot:sbopkg [2012/12/20 03:38 (UTC)] – [Using the Rename Option] spelling correction mfillpot
Line 55: 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.
  
 +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 cleate 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>
 +
 +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**
 +  * **-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)
 +  * **-u** - check for an update to sbopkg.
 +
 +<note warning>Current Working Point</note>
 +==== Application GUI Use ====
 +
 ===== Queue Files ===== ===== Queue Files =====
  

Trace:

wiki:user:mfillpot:sbopkg ()