[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.
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
wiki:user:mfillpot:sbopkg [2012/09/16 02:55 (UTC)] – [Sources] modified tags mfillpot | wiki:user:mfillpot:sbopkg [2012/12/20 03:38 (UTC)] – [Application CLI Use] added working point 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' | * **60-SBo-current.repo** - This is another custom repo file which by default is pointing to ponce' | ||
- | * **70-sb64.repo** - This file creates a repo option for the Slamd64 distribution' | ||
====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.</ | 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 warning> | + | Sometimes is 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/ |
+ | 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 **/ | ||
+ | < | ||
+ | i3=i3wm</ | ||
+ | |||
+ | 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 | + | |
+ | 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 ==== | ||
+ | < | ||
+ | |||
+ | 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. | ||
+ | < | ||
+ | |||
+ | Upon completion of the syncronization procedure you are free to build, install or inspect all slackbuild from http:// | ||
+ | |||
+ | === 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/ | ||
+ | * **-k** - skip selected process for installed application(s) | ||
+ | * **-u** - check for an update to sbopkg. | ||
+ | |||
+ | <note warning> | ||
+ | ==== Application GUI Use ==== | ||
+ | |||
===== Queue Files ===== | ===== Queue Files ===== | ||