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.
Can i make a feature request?
As your tool is very fast it would be cool if it could generate queue files as well.
It would definitely be possible to do that, but I'm not sure it makes sense as a feature, since sboui doesn't use queue files. What would be the intended use case? Are you just looking for something to replace the functionality of sqg, only faster?
Okay, well like I said, I don't think it really belongs as a feature for sboui. For one, because sboui doesn't use queue files, so it doesn't really make sense for it to generate them, and also because queue files are an sbopkg thing, and I don't want it to be focused on any specific package manager.
However, if it would be useful to you, I could post an unofficial patch that would allow sboui to generate queue files for the entire repo. Would you be interested in that? In the longer term, maybe it would be better to make a standalone sqg replacement using some of the sboui codebase, but I'm not going to promise that I will actually do that.
I have decided to give sboui a whirl. Spent a few hours using it to get familiar with it but didn't compile anything. Now I am using it on another desktop to compile filezilla and its dependencies. Nice! I like it a lot
If it is a lot of effort on you part, i would say don't do it, personally i could live without this functionality.
I think of it as a nice-to-have
I'll give it a try. I don't think it should be hard to do.
Quote:
Originally Posted by Gordie
I have decided to give sboui a whirl. Spent a few hours using it to get familiar with it but didn't compile anything. Now I am using it on another desktop to compile filezilla and its dependencies. Nice! I like it a lot
Thanks! Filezilla isn't one I've tested before, but I'm doing so now.
Great tool! I like the simplicity of the UI. Some things I noticed while testing:
Changing the default editor from vi to vim does not persist after restarting. vi is still the default editor after changing this setting.
Same as the above. Changing the repository directory setting does not persist. On my raspberry pi I use some non-standard paths in order to save files created to an external USB to lessen the amount of read/writes to the SD Card.
Using the w3m SlackBuild as an example. Unable to browse the patches directory. This is something that sbopkg doesn't include. It would be great feature to be able to review every file distributed with all SlackBuilds.
Again with w3m: After removing/installing/upgrading a package from the options menu, hitting dismiss, and hitting escape to return to the main menu, the screen is refreshed, then the filter for grouped packages resets, and the menu highlight moves back to the top of the list. This can be a bit annoying if a user has a ton of SlackBuilds installed and is trying to remove a few but has to keep moving the cursor back to a desired group -> SlackBuild. The only time this isn't an issue for me is when I search for a specific SlackBuild by name.
Great tool! I like the simplicity of the UI. Some things I noticed while testing:
Changing the default editor from vi to vim does not persist after restarting. vi is still the default editor after changing this setting.
Same as the above. Changing the repository directory setting does not persist. On my raspberry pi I use some non-standard paths in order to save files created to an external USB to lessen the amount of read/writes to the SD Card.
That's normal. Any settings that you want to persist should be set in /etc/sboui/sboui.conf or ~/.sboui.conf. The options window is just for temporary changes to settings during runtime.
Quote:
Originally Posted by mralk3
Using the w3m SlackBuild as an example. Unable to browse the patches directory. This is something that sbopkg doesn't include. It would be great feature to be able to review every file distributed with all SlackBuilds.
I was wondering if someone would mention that. Generally, the files in the top-level directory are the ones that people would most likely want to view, so I restricted the file browser to only let you view those. I'll try to work on letting you descend into lower directories for the next version.
Quote:
Originally Posted by mralk3
Again with w3m: After removing/installing/upgrading a package from the options menu, hitting dismiss, and hitting escape to return to the main menu, the screen is refreshed, then the filter for grouped packages resets, and the menu highlight moves back to the top of the list. This can be a bit annoying if a user has a ton of SlackBuilds installed and is trying to remove a few but has to keep moving the cursor back to a desired group -> SlackBuild. The only time this isn't an issue for me is when I search for a specific SlackBuild by name.
The reason I did that is because sometimes the lists change after installing/upgrading/removing/reinstalling. For example, if you have filtered by upgradable SlackBuilds, and you upgrade one, that one will no longer exist in the list after the operation. How would you like it to behave in such a case? Maybe after such an operation, it should check in the list to see if the previously highlighted item still exists, and if not jump back to the beginning (or maybe to the nearest one)? It sounds easy, but it becomes tricky especially if the category disappears from the filter after the changes are applied. Let me know how you think it should work, though.
(PS Ctrl-s will let you quickly jump back to wherever you want in the list.)
Last edited by montagdude; 05-15-2017 at 09:04 PM.
Reason: config file is /etc/sboui/sboui.conf, not /etc/sboui.conf
That's normal. Any settings that you want to persist should be set in /etc/sboui.conf or ~/.sboui.conf. The options window is just for temporary changes to settings during runtime.
I figured it was user error on my part. Thanks for clearing that up.
Quote:
Originally Posted by montagdude
The reason I did that is because sometimes the lists change after installing/upgrading/removing/reinstalling. For example, if you have filtered by upgradable SlackBuilds, and you upgrade one, that one will no longer exist in the list after the operation. How would you like it to behave in such a case? Maybe after such an operation, it should check in the list to see if the previously highlighted item still exists, and if not jump back to the beginning (or maybe to the nearest one)? It sounds easy, but it becomes tricky especially if the category disappears from the filter after the changes are applied. Let me know how you think it should work, though.
It depends on how the user is filtering. For unfiltered groups, it should jump back to the original Slackbuild since the list is so long. If its filtered by a specific Slackbuild name, then go back to the top. If filtered by installed, go back to the original Slackbuild. For upgradeable, go back to the top, since the list shouldn't show the SlackBuild in question any more.
I haven't played with any of the other filters yet so I am unable to say what the functionality for "tagged", "blacklisted", and "non-dependencies" should be.
Also, I just noticed you were wanting to remove a bunch of things at once. You might want to look into the tagging function (t or T). That's what it's designed for.
It depends on how the user is filtering. For unfiltered groups, it should jump back to the original Slackbuild since the list is so long. If its filtered by a specific Slackbuild name, then go back to the top. If filtered by installed, go back to the original Slackbuild. For upgradeable, go back to the top, since the list shouldn't show the SlackBuild in question any more.
Ah, but what about if you are using the Installed filter and removing a SlackBuild. Then that list will change too. You see, it gets complicated. I think that maybe the best way to do it would be to highlight the same item by number in the list after doing an install/upgrade/reinstall/remove, unless the category disappeared. That way, either the same one will be highlighted (if the list stayed the same) or one next to it. I'll mess around with it, anyway.
I figured it was user error on my part. Thanks for clearing that up.
It depends on how the user is filtering. For unfiltered groups, it should jump back to the original Slackbuild since the list is so long. If its filtered by a specific Slackbuild name, then go back to the top. If filtered by installed, go back to the original Slackbuild. For upgradeable, go back to the top, since the list shouldn't show the SlackBuild in question any more.
I haven't played with any of the other filters yet so I am unable to say what the functionality for "tagged", "blacklisted", and "non-dependencies" should be.
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!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.