[SOLVED] Correct universal way of building/installing SBo package in batch mode?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
sbopkg -h
sbopkg 0.38.1
Usage: sbopkg [OPTIONS] <packagename(s)>
Options are:
-b pkg/queue(s) Build the specified package(s). If one or more queuefiles
are specified, build the packages they refer to.
-B Bulk process the queue without confirmation.
-c Check for updates to installed packages.
-D localdir Location of local copy of the repositories.
-d pkg/queue(s) Like '-b', but only download sources.
-e error_action Specify what sbopkg is supposed to do on build errors.
Valid options are: ask (default), continue, stop.
-f file Override default configuration file with specified file.
-g package(s) General search for packages matching string.
-h Display this help message.
-i pkg/queue(s) Like '-b', but also install built packages.
-k Skip installed packages when building.
-l Display the repo's ChangeLog.txt and then quit.
-o Display the obsolete source files & prompt for deletion.
-P List uninstalled cached package files & prompt for deletion.
-p List installed packages from active repo.
-q Quiet some of the command-line output.
-R When combined with -b or -i, preview the READMEs of the
packages to be built/installed before starting the build
process. When combined with -p, show the READMEs of all
installed packages from the active repo.
-r Sync the remote repository with the local mirror and then
quit.
-S Use sandbox when building packages.
-s package(s) Specific search by specific package and, if found,
display package information.
-u Check for an update to sbopkg.
-V repo/branch Set the repository/branch. The repo is optional and, if
not given, sbopkg will try to make the best match,
starting with the default repo. For a list of valid repos,
issue '-V ?'
-v Print sbopkg's version on stdout.
Note: multiple arguments to -b, -g, -i, and -s must be quoted ("pkg1 pkg2") or
can be specified multiple times (-i foo -i bar). If using the latter syntax,
build options may also be passed on the command line on a per app basis using
the -b or -i flags in colon-separated groups (where whitespace must also be
quoted). For example, '-i app:opt1="arg1 arg2":opt2=arg1 app2'
I gave it some more thought and now I'm not even sure if I should use the patch that I attached a few posts above. Since it's possible to explicitly tell sbopkg to use a queue by using APPNAME.sqf rather than APPNAME, as @drumz pointed above, then I assume it's also possible to tell sbopkg to use the APPNAME as package, by making sure that there's no queue with the same name as well. This can be done by explicitly removing the queue with the same name if it exists, since generating it again later if needed is not a resource hog. Not having a queue also removes the ambiguous scenario when there's both a package and a queue with the same name.
So:
1. If I want to use APPNAME as queue, I should explicitly pass APPNAME.sqf (generate it if needed) to sbopkg
2. If I want to use APPNAME as package, I should remove APPNAME.sqf if it exists, before passing APPNAME to sbopkg
This would allow to use sbopkg as it is now without the patch applied. This would make sure sbookg will never ask me to use the package or the queue, since I'm explicitly telling it to use the queue when I need that. And this would make sure that whenever I need sbopkg to run the package, I'll never run into ambiguity either, since I'm making sure there's no queue with same name.
So basically sbopkg will find APPNAME according to the repository and queue based on what's inside queue directory. In the latest sbopkg (in git master), it has an ability to generate custom queue and install it from that custom queue.
I just made a custom queue for virt-manager last night and install it as virt-manager_current.sqf in /var/lib/sbopkg/queue and i can install it using sbopkg -i virt-manager_current
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.