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.
When doing a fresh re-install [1], you're likely installing a LOT of packages, from Alien Bob, Flatpaks, and sbopkg.
So, specifically, sbopkg is the subject of my question. How do you configure it (options, etc.) to install everything that builds successfully non-stop, and save the constant failed packages to the end to try again (might have been a network issue the first time) so you don't have to sit and wait to hit "y" again for 30 minutes to an hour PER CATEGORY?
If this is not possible now, I'd like to suggest this as a possible improvement, if it's possible in the menu package it uses.
Thanks
[1] (VokoscreenNG's uninstall package said it was going to remove its directory ... ok, ..../vokoscreenng, right? Nope, /usr/bin. And since you have to do the uninstall as root,,,)
well, you can't since some packages depends on other packages and if one of those dependencies failed to build for any reason, the next package will fail as well
Assuming you've built all the queues ahead of time with "sqg", here's how I do what it sounds like you want to do:
Code:
# remove the -R or -k if you don't want to look at all the README's or skip already installed slackbuilds
# the important bit is "-e continue" to build non-stop
sbopkg -R -B -k -e continue -i "slackbuild1 slackbuild2 slackbuild3"
Then go through the summary output and look for stuff that failed to build and try building those manually or look through the sbopkg log file (/var/log/sbopkg/sbopkg-build-log) for the build errors.
Assuming you've built all the queues ahead of time with "sqg", here's how I do what it sounds like you want to do:
Code:
# remove the -R or -k if you don't want to look at all the README's or skip already installed slackbuilds
# the important bit is "-e continue" to build non-stop
sbopkg -R -B -k -e continue -i "slackbuild1 slackbuild2 slackbuild3"
Then go through the summary output and look for stuff that failed to build and try building those manually or look through the sbopkg log file (/var/log/sbopkg/sbopkg-build-log) for the build errors.
And THAT is exactly what I was looking for. Thank you so much!
Except for one problem: it won't run with -e continue. That IS in the man page (first thing I checked), so it SHOULD be fine....but it just isn't. No idea why.
Just a side comment .... Just going through the misc section in sbopkg, I found a sorted grep. Why would anyone want that when you can just pipe the output from grep to sort? :-)
And THAT is exactly what I was looking for. Thank you so much!
Except for one problem: it won't run with -e continue. That IS in the man page (first thing I checked), so it SHOULD be fine....but it just isn't. No idea why.
Can you paste the exact command and error that doesn't work?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.