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.
Not CMakeLists.txt, but CMakeCache.txt, in the build/ directory. It looks like libconfig++ is built correctly from your other output, so I'm curious as to why it is not linking.
Oops. I misread that. Sorry about that. The output returned is:
Well, that looks correct too, and I just tried building both libconfig++ and sboui on a clean, up-to-date -current, and it works fine, so I'm kind of stumped here. You are building the latest, version 2.0.1, and not setting any unusual environment variables that might change the compiler or linker, correct? All I can think of to try now would be:
1) Rebuild both libconfig and sboui and see if that fixes it.
2) In sboui.SlackBuild, add VERBOSE=1 after $BUILDCMD on line 101. When you build again, the linking line should look something like this. Note in particular the -lconfig++ at the end:
Well, that looks correct too, and I just tried building both libconfig++ and sboui on a clean, up-to-date -current, and it works fine, so I'm kind of stumped here. You are building the latest, version 2.0.1, and not setting any unusual environment variables that might change the compiler or linker, correct? All I can think of to try now would be:
1) Rebuild both libconfig and sboui and see if that fixes it.
2) In sboui.SlackBuild, add VERBOSE=1 after $BUILDCMD on line 101. When you build again, the linking line should look something like this. Note in particular the -lconfig++ at the end:
Well, it appears I goofed. I was using the SlackBuild for 1.0, and when I tried to extract the .tar.gz for the SlackBuild into the existing directory to update the SlackBuild, I accidentally made a subdirectory of sboui instead of overwriting and updating the files already there. It worked perfectly this time. Sorry for all the trouble. Goofiness on my part.
Last edited by 1337_powerslacker; 01-01-2019 at 10:48 PM.
Well, it appears I goofed. I was using the SlackBuild for 1.0, and when I tried to extract the .tar.gz for the SlackBuild into the existing directory to update the SlackBuild, I accidentally made a subdirectory of sboui instead of overwriting and updating the files already there. It worked perfectly this time. Sorry for all the trouble. Goofiness on my part.
Not really sure this is the place for this but here goes.
Sboui is the only place this problem (if it actually is a problem) shows up. I have an icon for sboui and it brings up a dialog box for "KDE su" with a place for root's password and a checkbox for "remember password".
For a short time it will actually remember the password but frequently it forgets. Not because I reboot or even logout/login. Maybe because zscreensaver came on?
Is this normal? If not, what can I do to change things?
Thanks montagdude. In this house it is strange for me. One user nly on "my" computer, ME and my wife doesn't give a hoot about Linux and she stays on her own computer so no security issues. Just seemed strange is all. Thanks again.
Thanks montagdude. In this house it is strange for me. One user nly on "my" computer, ME and my wife doesn't give a hoot about Linux and she stays on her own computer so no security issues. Just seemed strange is all. Thanks again.
If you want this feature, you might give gksu (available on SlackBuilds.org) a try instead of kdesu. It also has an option to remember the password, but with two sub-options: save for this session, or save in the keyring. I think the latter would make it remember it forever, or until you remove it from the keyring. I don't use that feature myself. To make the desktop file launch sboui via gksu instead of kdesu, rebuild sboui with the build option GRAPHICAL_SU=gksu.
Quote:
Originally Posted by Gordie
By the way, I just love sboui
I'm glad you like it. I'm rather fond of it myself.
If you want this feature, you might give gksu (available on SlackBuilds.org) a try instead of kdesu. It also has an option to remember the password, but with two sub-options: save for this session, or save in the keyring. I think the latter would make it remember it forever, or until you remove it from the keyring. I don't use that feature myself. To make the desktop file launch sboui via gksu instead of kdesu, rebuild sboui with the build option GRAPHICAL_SU=gksu.
I'm glad you like it. I'm rather fond of it myself.
Oh boy does gksu ever change things for the better for me. Thank you so much
I tried sboui about when it came out, love the idea, but couldn't figure out configuration. Now I think I did--for SlackBuilds.org (SBo) only--but might want to use other repositories. Currently I'm on Slackware-current and want to use SBo-git (i.e., sbo-current) but sboui is saying I'm using 14.2... is that not the case, or can anyone explain what's different or how the configuration should be?
I tried sboui about when it came out, love the idea, but couldn't figure out configuration. Now I think I did--for SllackBuilds.org (SBo) only--but might want to use other repositories. Currently I'm on Slackware-current and want to use SBo-git (i.e., sbo-current) but sboui is saying I'm using 14.2... is that not the case, or can anyone explain what's different or how the configuration should be?
First off, if you aren't already doing this, for -current it is better to build sboui from the latest commit to master rather than the 2.1 release. The 2.1 release will still work on -current, but master has some additional improvements that are helpful.
Just for some background information, you may or may not already be aware, but sboui is designed as an interface that can work with a number of backend package managers, including the built-in one (a.k.a. sboui-backend), sbopkg, or sbotools. Configuration of sboui to use Ponce's repository for -current is mainly a matter of configuring the backend package manager. Personally, I use the built-in one and run -current. Here is my sboui-backend.conf:
Code:
#
# Configuration file for sboui-backend
#
# Repository to use. Note Ponce repo is for -current only.
#REPO=git://git.slackbuilds.org/slackbuilds.git
REPO=git://github.com/Ponce/slackbuilds.git
# Branch (not applicable to Ponce repo). e.g., master, 14.2, 14.1, etc.
BRANCH=14.2
# Location to clone git repository
REPO_DIR=/var/lib/sboui/repo
# Whether to remove built package after installing (yes/no)
CLEAN_PACKAGE=no
# Whether to remove temporary source and package directories after building
CLEAN_TMP=no
I haven't tried using sbopkg or sbotools with -current, so I don't know how to configure them to use Ponce's repo, but I do believe that both of them have the capability. If you stick with the built-in package manager as the backend, then you can just use the above.
Last edited by montagdude; 05-20-2020 at 10:38 PM.
@montagdude did you ever consider ktsuss (keep the su simple, stupid) integration rathter than gksu or kdesu? I am interested in the systray update notifier, but not really interested in all the cascade of libraries for gksu and python. I too love sboui and the integration with sbotools for build. There is still one feature enhancment I'm interested in which is to continue a build if the MD5SUM or SHA fail, like sbopkg allows. This is helpful when attempting to build from source a package version newer than what is in SBo. I simple modify slackbuild and info, then say yes proceed with build when the hash check is different, since I KNOW it will be different. Just curious, Cheers, BrianA_MN
First off, if you aren't already doing this, for -current it is better to build sboui from the latest commit to master rather than the 2.1 release. The 2.1 release will still work on -current, but master has some additional improvements that are helpful. [...]
Thanks for all that, but shouldn't sboui commits be added to SBo-git? I finally got sbopkg, sbotools setup to use SBo-git... but don't have sboui-git...
@montagdude did you ever consider ktsuss (keep the su simple, stupid) integration rathter than gksu or kdesu? I am interested in the systray update notifier, but not really interested in all the cascade of libraries for gksu and python. I too love sboui and the integration with sbotools for build. There is still one feature enhancment I'm interested in which is to continue a build if the MD5SUM or SHA fail, like sbopkg allows. This is helpful when attempting to build from source a package version newer than what is in SBo. I simple modify slackbuild and info, then say yes proceed with build when the hash check is different, since I KNOW it will be different. Just curious, Cheers, BrianA_MN
I think ktsuss should work. Check the README for a build flag to tell it which one you intend to use at compile time. I think it is GRAPHICAL_SU=ktsuss, but I don't remember for sure off the top of my head.
Your suggestion about an option to allow the build to proceed if the MD5sum fails seems like a good one. I will add that to the TODO list. Thanks.
Thanks for all that, but shouldn't sboui commits be added to SBo-git? I finally got sbopkg, sbotools setup to use SBo-git... but don't have sboui-git...
I will eventually pull in the changes into a new release. The changes aren't significant enough to warrant ponce's branch pointing to a different version. For now, just use the same build script that is already in the repo but change the version number to match the link I gave you, and put the tarball in the build directory.
Last edited by montagdude; 05-23-2020 at 11:37 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
