[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.
Next revision | Previous revisionNext revisionBoth sides next revision | ||
wiki:user:mfillpot:sbopkg [2012/09/01 01:05 (UTC)] – created mfillpot | wiki:user:mfillpot:sbopkg [2012/12/20 03:38 (UTC)] – [Using the Rename Option] spelling correction mfillpot | ||
---|---|---|---|
Line 1: | Line 1: | ||
<!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> | <!-- Add your text below. We strongly advise to start with a Headline (see button bar above). --> | ||
+ | |||
====== sbopkg ====== | ====== sbopkg ====== | ||
- | < | + | sbopkg |
- | sbopkg | + | The queue file use tool included in sbopkg |
+ | <note warning> | ||
- | ======Installation====== | + | =====Installation===== |
- | ===== Obtaining sbopkg | + | ==== Obtaining sbopkg ==== |
The sbopkg application is found on the project' | The sbopkg application is found on the project' | ||
Once you locate the download button use your favorite download manager to download the resulting package into your chosen directory. | Once you locate the download button use your favorite download manager to download the resulting package into your chosen directory. | ||
- | ===== Installing sbopkg | + | ==== Installing sbopkg ==== |
Once the download has completed you will need to enter your root or priveledged account to run the installation application. \\ | Once the download has completed you will need to enter your root or priveledged account to run the installation application. \\ | ||
Enter the chosen download directory and enter the following, substituting the version number with the current version. | Enter the chosen download directory and enter the following, substituting the version number with the current version. | ||
< | < | ||
- | ======Application Configuration====== | + | =====Application Configuration===== |
- | < | + | < |
All configuration files for sbopkg are kept in the **/ | All configuration files for sbopkg are kept in the **/ | ||
- | =====Editing sbopkg.conf===== | + | ====Editing sbopkg.conf==== |
- | + | < | |
- | < | + | **man 5 sbopkg.conf**</ |
- | **man 5 sbopkg.conf</ | + | |
The sbopkg.conf file is well documented with comments explaining the various options, read the comments associated with the option that you wish to change to confirm that the syntax and chosen options are correct. | The sbopkg.conf file is well documented with comments explaining the various options, read the comments associated with the option that you wish to change to confirm that the syntax and chosen options are correct. | ||
+ | The only modifications that should be performed on this file without potential issues are to move the directories that the application will use, which are listed below: \\ | ||
+ | * **OUTPUT** | ||
+ | * **QUEUEDIR** | ||
+ | * **REPO_ROOT** - The directory which will the synchronized slackbuild scripts | ||
+ | * **SRCDIR** - The directory which will contain the downloaded source archives for all builds | ||
+ | |||
+ | You can optionally modify REPO_BRANCH and REPO_NAME variables if you wish to use a custom repository, however the official SlackBuilds.org repo for the current stable Slackware release is enabled by default. | ||
+ | |||
+ | ====Selecting Repos (Optional)==== | ||
+ | <note important> | ||
+ | |||
+ | All files in the repos.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.</ | ||
+ | |||
+ | The repos.d directory currently contains the following files: \\ | ||
+ | * **README** - The author' | ||
+ | * **40-sbo-repo** - The author' | ||
+ | * **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' | ||
+ | |||
+ | ====Using the Rename Option==== | ||
+ | <note important> | ||
+ | |||
+ | 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.</ | ||
+ | |||
+ | 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 **/ | ||
+ | |||
+ | 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 ===== | ||
+ | |||
+ | 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 ==== | ||
+ | < | ||
+ | |||
+ | 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 ===== | ||
+ | |||
+ | ===== Making Sbopkg Handle Dependencies ===== | ||
+ | ====== Notes about Hard Drive Use ====== | ||
+ | |||
+ | <!-- | ||
+ | Now, run the command //sbopkg// to execute the application which will do the initial file setup and synchronization, | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | This will ask for an option to create a list of directories to maintain its data base. Hit the key, //' | ||
+ | |||
+ | |||
+ | |||
+ | ===== Making Sbopkg Handle Dependencies ===== | ||
+ | |||
+ | By default this sbopkg, dont have automatic dependency check. But, it can be done using the following | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | Previously, there will be two directories.After the above command, one more new directory, called sbopkg-slackware-queues will get added.By default the directory //queues// get checked. Now, by making a soft link named //queues// to the // | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | Now, just check it, using\\ | ||
+ | |||
+ | < | ||
+ | |||
+ | or\\ | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | Now, to update the queue files periodically, | ||
+ | |||
+ | < | ||
+ | |||
+ | Enable a mirror, by removing the comment symbol(#), save and exit the file.\\ | ||
+ | |||
+ | |||
+ | |||
+ | Run the following commands, to get the gpg key for image validation. | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | after the key has been downloaded, issue the command, //slackpkg update// to grab the new changelog\\ | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | Update the queue files, | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | === Installing a package using sbopkg === | ||
+ | |||
+ | |||
+ | |||
+ | The default syntax is, //sbopkg -i < | ||
+ | |||
+ | < | ||
+ | |||
+ | This will give the user, an option to use Queue File or not to use.Use the Queue File to handle dependencies automatically.A package will be placed in ///tmp// location.These packages can be moved to anyother place in the disk, so that no need to download each and every time. \\ | ||
+ | |||
+ | |||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | Now, the //sl// application is installed. This application can **NOT** be run as root user | ||
+ | |||
+ | < | ||
+ | |||
+ | |||
+ | |||
+ | User can browse the repository, if the exact package name is not known. There are two [ but not limited to ] ways to do that.\\ | ||
+ | < | ||
+ | and browse this command-line based application. Or , visit http:// | ||
+ | --> | ||
+ | |||
====== Sources ====== | ====== Sources ====== | ||
- | <!-- If you are copying information from another source, then specify that source --> | ||
- | <!-- * Original source: [[http:// | ||
<!-- Authors are allowed to give credit to themselves! --> | <!-- Authors are allowed to give credit to themselves! --> | ||
* Originally written by [[wiki: | * Originally written by [[wiki: | ||
- | * Contrbutions by [[wiki: | + | * Contrbutions by [[wiki: |
<!-- 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 " | <!-- You must also remove the tag-word " | ||
- | {{tag> | + | {{tag>author_mfillpot |