sboui: ncurses-based UI for SBo package managers (call for testers)
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.
I've made two changes in the development branch. One is to try to restore the original selection as closely as possible after installing, upgrading, etc. The other is to allow browsing and viewing files in subdirectories. They will go into the next release. Good suggestions, by the way!
Sweet. I was out of town for a few days. I will take a look at it some time tonight or tomorrow. Thanks for the hard work.
You'll just need to edit the version in the SlackBuild to match.
This latest commit also has one more enhancement since the last time I posted, which is to provide a convenient way to view the README and other files, set build options, and view package/version info for dependencies directly before installing, upgrading, etc. That was something that I decided to add when I was building python3-matplotlib and wanted to check READMEs and possibly set build options for everything in the build order. The other way would be to tag all the dependencies and then filter by tagged SlackBuilds, but this new way is much more convenient.
Last edited by montagdude; 05-22-2017 at 10:26 PM.
Reason: added some more info
I just finished testing 0.4_development branch and everything works great. I will continue to use it to see if there is something else that might be a good enhancement. Thanks again.
I've been kind of sitting on this for awhile without releasing it, but anyway here is an update to 0.4.2. There were a couple 0.4.x releases that I didn't update on SBo. Main changes since 0.3.1:
Preserve previous selection as closely as possible after installing, upgrading, etc.
Allow browsing files in subdirectories of a SlackBuild.
View READMEs, browse files, set build options, and show package info for dependencies (use the "a" hotkey in the dialog box listing the dependencies).
Improve logic for determining when a package is upgradable.(With previous versions, it was possible for some to slip through the cracks in some uncommon situations.)
Color themes are now read automatically from /usr/share/sboui/themes and ~/.local/share/sboui/themes. As a consequence, the color_theme_file input has been removed. Just put custom themes in one of these directories, and they will be picked up.
One additional variable is now required for color themes: theme_name.
Build options can now be entered one per line in the build options dialog box (see example). You can also still enter them all the old way on a single line if you want.
Just tested out 0.3.1 on 14.2 on an old sun ultra 40 workstation I use and with 176 slackbuild.org packages installed it loads up in a 1-3 seconds. I'm really liking the interface.
I look forward to playing with it more in the future
I have been using sboui since the first page of this thread. Just last night I used it for KODI and aside from some deps that were not expected everything worked. The deps I speak of are not the fault of sboui
Hi montagdude, I want to report a potential bug with the 0.4.2 version of sboui.
I received the following error when trying to use regular sbotools to remove a SBo package, which worked without flaw until the latest sboui upgrade.
root@Hicrest1:/home/brian/Downloads/QEMUImages# sboremove winetricks
Can't use an undefined value as an ARRAY reference at /usr/sbin/sboremove line 139.
root@Hicrest1:/home/brian/Downloads/QEMUImages# sbofind winetricks
SBo: winetricks 20170614
Path: /usr/sbo/repo/system/winetricks
root@Hicrest1:/home/brian/Downloads/QEMUImages# sboremove winetricks-20170614-noarch-1_SBo
Unable to locate winetricks-20170614-noarch-1_SBo in the SlackBuilds.org tree.
root@Hicrest1:/home/brian/Downloads/QEMUImages# sboremove winetricks
Can't use an undefined value as an ARRAY reference at /usr/sbin/sboremove line 139.
root@Hicrest1:/home/brian/Downloads/QEMUImages# sboui
As you can see when using the sboui interface the same package was in fact removed.
I noticed that when upgrade sboui from 3.1 to 4.2 it attempted to update the config file, which I rejected after reviewing the changes because the changes were to revert the existing conf file back to sbopkg settings.
Other environment factors. System is Slackware 14.2 multilib enabled. SBo database sync same day before attempt. SBoTools sboinstall/sbofind of same package worked without issue. Using default location for SBo database.
How can I help with further testing to flush out this bug?
I guess I'm a little confused, because as far as I can tell, that looks like a bug with sbotools, not sboui. sboui doesn't use the SBo package manager (sbopkg, sbotools, etc.) to remove packages, it just uses removepkg. Hence why it worked when you removed it through sboui, but not with plain sbotools.
Just to clarify, did you intentionally remove cabextract also?
sboui doesn't use the SBo package manager (sbopkg, sbotools, etc.) to remove packages, it just uses removepkg.
OK, my error, I was under the impression that sboui was using the full toolset from sbopkg and sbotools. I guess it is only using the database of either as selected in the conf. But then why does the conf include the install and search commands of the pkg selected?
Quote:
Originally Posted by montagdude
Just to clarify, did you intentionally remove cabextract also?
OK, my error, I was under the impression that sboui was using the full toolset from sbopkg and sbotools. I guess it is only using the database of either as selected in the conf. But then why does the conf include the install and search commands of the pkg selected?
Yes.
It uses the repo, sync command, install command, and upgrade command from the package manager, but not the remove command. Partially because there's no reason not to just use removepkg, and partly because as I recall sbopkg doesn't even have a remove command.
Yes, I know that. I said sbopkg doesn't have a remove command (plus, there's no reason for sboui to do `sboremove pkgname` when it could just do `removepkg pkgname`). Did you figure out your issue with sboremove?
I just tried to search for virus with sboui and did the same search for virus at slackbuilds.org There are totally different results
That's not surprising, because the webpage also searches based on the keywords maintainers enter when they submit a script, and in different branches of the repo (14.2, 14.1, etc.). sboui only searches in the name and (optionally) READMEs. Keywords are not available in the local repo as far as I know.
That's not surprising, because the webpage also searches based on the keywords maintainers enter when they submit a script, and in different branches of the repo (14.2, 14.1, etc.). sboui only searches in the name and (optionally) READMEs. Keywords are not available in the local repo as far as I know.
That means to me that I would have to know exactly what I am looking for so would not need a search. sboui came up blank with that search. Blank is not very useful
Getting results now. Will keep trying. I prefer sboui to anything else so far
Last edited by Gordie; 07-20-2017 at 07:36 PM.
Reason: OK - tried using the "Search READMEs" feature. Takes a long time but at least it works. I'm learnin
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
