sboui: ncurses-based UI for SBo package managers (call for testers)

Stable version works... don't know if I need current version but the below happens.

user@host:~/sboui-d078904ad3bdfed5b07339c4257dc407ce91130b/build$ make
[  1%] Linking CXX executable sboui
/usr/bin/ld: cannot find -ltinfo
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/sboui.dir/build.make:872: sboui] Error 1
make[1]: *** [CMakeFiles/Makefile2:96: CMakeFiles/sboui.dir/all] Error 2
make: *** [Makefile:150: all] Error 2

Originally Posted by dchmelik Stable version works... don't know if I need current version but the below happens. user@host:~/sboui-d078904ad3bdfed5b07339c4257dc407ce91130b/build$ make [ 1%] Linking CXX executable sboui /usr/bin/ld: cannot find -ltinfo collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/sboui.dir/build.make:872: sboui] Error 1 make[1]: *** [CMakeFiles/Makefile2:96: CMakeFiles/sboui.dir/all] Error 2 make: *** [Makefile:150: all] Error 2

It builds fine here. Why are you running make from inside the source directory? Just run the SlackBuild from SBo with this change:

VERSION=${VERSION:-d078904ad3bdfed5b07339c4257dc407ce91130b}

Originally Posted by montagdude It builds fine here. Why are you running make from inside the source directory? Just run the SlackBuild from SBo with this change: VERSION=${VERSION:-d078904ad3bdfed5b07339c4257dc407ce91130b}

Done. Same thing happened.

Originally Posted by dchmelik Done. Same thing happened.

I just built it on a clean, up-to-date -current and it worked fine. And there's nothing in the new version that would cause any difference in linking compared to 2.1, so I think you must either have something wrong with your system or be doing something wrong when you try to build. I can give you the package I just built if you want. FYI, this commit is the only significant difference between 2.1 and the latest master:

Create complete-as-possible build order when deps are missing This is a follow-on to 66b6add, which allowed the build to proceed but stopped computing the build order when a dependency was missing in the chain. This commit continues computing the build order, skipping any missing dependencies, in such cases. A warning is still presented to the user.

This is helpful for -current, because SlackBuilds get removed from the tree when they are added by Pat. This allows the build order to be created correctly even though some dependencies are missing from the tree (but present in the base system).

It's been a while since I did any development work on sboui (or anything really), but I just added a feature that some were asking for. If you use the default built-in backend, you can now choose whether to continue or stop if a source tarball fails the MD5sum check. The main use is for people who build newer versions of packages than are in the repository and don't want to edit the MD5sum in the .info file. This change has been pushed to master on Github, so you can build it yourself if desired. I have a few other improvements on my list before tagging a new release and updating it on SBo.

Hi Montagdude you do realize libconfig is a dependency.
You may want to put that on your README.md
Just a thought.

Yes, I'm aware of that. It's in the .info file if you install it from SBo. I don't normally put required dependencies in README.md, since you'll find out if you're missing it anyway when you go to build it. Technically speaking, libconfig isn't the only required dependency, it's just the only one that's not present in a full Slackware install.

After nearly two and a half years, I'm pleased to announce a new release of sboui, version 2.2. The update has been pushed to SBo. Here are the main enhancements since 2.1 was released:

• Add an option for filters to work cumulatively, which is the new default (see cumulative_filters option in sboui.conf). Cumulative filters also apply to searches. To clear all filters, just do "Filter All" first.
• Make blacklist also apply to non-installed SlackBuilds to prevent them from being installed. The blacklist file, previously named 'package_blacklist', has been renamed to 'blacklist'. (If you upgrade sboui using the script from SBo, it will handle creating a copy of your existing package_blacklist -> blacklist.)
• Create complete-as-possible build order when deps are missing. This enhancement helps especially for the -current SBo repo, where deps may have been moved to the main Slackware tree but still listed in the SBo .info files.
• Add an option to keep source tarballs in the default backend (see CLEAN_SOURCE option in sboui-backend.conf). Source tarballs are retained next to the SlackBuild in the local repo tree.
• Add an option to continue with the build when the MD5sum check fails for a source tarball.

Montagdude, I upgraded to v. 2.2 but with the built-in package manager still doesn't recognize the 15.0 branch:

error: pathspec '15.0' did not match any file(s) known to git

This is my sboui-backend.conf

REPO=git://git.slackbuilds.org/slackbuilds.git
BRANCH=15.0

Originally Posted by roberto967 Montagdude, I upgraded to v. 2.2 but with the built-in package manager still doesn't recognize the 15.0 branch: error: pathspec '15.0' did not match any file(s) known to git This is my sboui-backend.conf REPO=git://git.slackbuilds.org/slackbuilds.git BRANCH=15.0

Hm, I had that too very early on after the 15.0 branch was first released, but I haven't been able to reproduce it since then. Someone else said the same in an issue for sboui on github. I assumed it was an upstream problem. Can you try just deleting your local copy of the repo (rm -rf /var/lib/sboui/repo) and syncing again?

Originally Posted by montagdude Hm, I had that too very early on after the 15.0 branch was first released, but I haven't been able to reproduce it since then. Someone else said the same in an issue for sboui on github. I assumed it was an upstream problem. Can you try just deleting your local copy of the repo (rm -rf /var/lib/sboui/repo) and syncing again?

removing and syncing again solved my problem. Thank you

I just pushed sboui version 2.3. The default search behavior in 2.2 was tripping a lot of people up, including me a couple times, because by default it would operate on the current filtered list of SlackBuilds only instead of the entire repository. In 2.3 it searches the entire repository by default again, but there is an option added in the search dialog to operate on the current list only. That way you can have the best of both worlds. The new version is on Github now and should also be in the next SBo update as long as I didn't mess anything up with the submission.

Originally Posted by montagdude I just pushed sboui version 2.3. The default search behavior in 2.2 was tripping a lot of people up, including me a couple times, because by default it would operate on the current filtered list of SlackBuilds only instead of the entire repository. In 2.3 it searches the entire repository by default again, but there is an option added in the search dialog to operate on the current list only. That way you can have the best of both worlds. The new version is on Github now and should also be in the next SBo update as long as I didn't mess anything up with the submission.

Well it is at SlackBuilds.org as we speak. I am downloading it now then going to bed

@montagdude:
Alien bob provides quite a number of slackbuilds.
https://slackware.nl/slackbuilds.org/15.0/

As much as ponce:
https://github.com/Ponce/slackbuilds

Is it possible to have access to these also thru sboui?

Hi
Your first link is for a mirrored slackbuilds.org repo.
The second is for the forked repo maintained for current by ponce (see sticky post, especially first post).
Nothing to add I believe.

Regards