A graphical user interface for sbopkg based on PyQt
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.
Looks nice but doesn't start here yet (not clean at all Slackware 14.1 32-bit):
Code:
bash-4.2# sbopkg_gui
Traceback (most recent call last):
File "/usr/bin/sbopkg_gui", line 552, in <module>
window = MainWindow()
File "/usr/bin/sbopkg_gui", line 171, in __init__
self.init_slackbuilds()
File "/usr/bin/sbopkg_gui", line 209, in init_slackbuilds
version = elements[len(elements)-3]
IndexError: list index out of range
bash-4.2#
If you need more info, just ask (tomorrow: 1:24 AM here).
PS I forgot: Welcome to this forum!
Last edited by Didier Spaier; 06-21-2016 at 04:56 AM.
Reason: PS added.
works fine on Slackware64 14.1 here. It is interesting to see that the program also considers packages that were not installed from SBo, but are nevertheless available at SBo. For example I have a lot of things installed from SlackOnly and sbopkg gui sees them fine and warns that they were installed from an alternative source.
Installed dependencies are listed in green, which is useful. However, dependencies are listed on a single row, hence when they are too many a user cannot see them all, unless the window is stretched.
I just gave it a try, and it works well. It recognized and warned about re-installing packages that came from a different repository, which is helpful. One thing that is a bit inconvenient about it is that it requires sudo for every command, and it gets tedious entering your password many times. I recognize that this is because the GUI is normally run as a regular user, so I'm not sure if there's a way around that. Maybe kdesu or similar?
Other than that, in some ways this is very similar to the ncurses UI I've written, called sboui, that works with sbopkg, sbotools, etc. If you don't mind, I can share some things that I've put into that tool that I think would be helpful with this too:
Allowing the user to modify sbopkg command line options and set global environment variables. For example, I like to use MAKEFLAGS="-j 4" with SlackBuild scripts to compile in parallel by default.
Considering above, it's not much more of a step to also support sbotools and custom package managers, if you allow the install and upgrade commands to be variable. Of course, it's totally up to you if you actually want your tool to do that. Feel free to borrow from sboui's source code or default configuration file if you are interested.
sbopkg_gui says that my virtualbox-kernel can be upgraded, but it is actually at the latest version. The SlackBuild appends _$(uname -r) to the version number, so maybe that's why? I'm also running a non-default kernel. I'm not sure what criteria sbopkg_gui uses to determine what is upgradable.
Hopefully that is helpful, and thanks for sharing this tool!
Last edited by montagdude; 05-01-2017 at 08:45 PM.
You're always welcome to start your own thread rather than resurrecting an old one.
In regards to this error, my first guess is that you don't have the version set up, but I've never used sbopkg_gui, so I don't know what it needs set itself vs what it uses of from the regular sbopkg.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.