Hello,

I've just installed full Slackware (current) after last using it back in version 3.0.

All's is well and so far very impressive.
Just one very silly thing I ran into almost immediately by pure chance.
Once I loaded up KDE I went ahead and fired up Kigo - The Go game but ran into an error saying "Kigo was unable to find a Go engine backend."
Obviously, the engine package is missing from the installation.

Like I said. A "Bug". I almost feel ashamed reporting this, but still.

All the best,
Chris.

Slackware does not ship a GO backend engine, it has to make choices on what to include. You can obtain a build script for GnuGO from SlackBuilds.org and then compile the package yourself: https://slackbuilds.org/repository/14.2/games/gnugo/

2 members found this post helpful.

From https://docs.kde.org/stable5/en/kigo...iguration.html :

"Kigo needs a valid backend to function properly. As you can see in the screenshot below, it used GnuGo by default."

Now gnugo is not part of slackware but you can build your own gnugo package, preferably with Ponce's buildscript for -current:

https://github.com/Ponce/slackbuilds...nt/games/gnugo

You might argue that since slackware -current ships kigo it should also ship gnugo. I don't use KDE myself, so I have no decided opinion in the matter.

Oops. Beaten to it with several minutes.

That's exactly my argument.
If Kigo is present in the full installation, it should be functional.
I have no problem with it not being included at all, but launching something that's there by default only to find out there's a piece missing that inhibits its function really hurts the experience.

13 members found this post helpful.

Yes I understand.
However, as I said in a previous reply,
Since the package is present in the full installation, it should be functional or not be there at all.
Running into a loading error in a built-in package that's a part of a default full installation really hurts the experience.

I very much enjoy re-discovering Slackware after all these years and once again having the feel of controlling the system like in the old days.

4 members found this post helpful.

I made my argument, you can do with it as you please of course, including disagreeing.
Well you are in control of your Slackware installation. It's as simple as "sbopkg -r && sbopkg -k -i gnugo". Oh wait, sbopkg is not part of Slackware core distro! It is a bug! Or is it? Slackware is your Swiss army knife, it is capable of a lot of things but bottom line: it is all about what you do with it.

5 members found this post helpful.

I shall add that SBo is endorsed by our BDFL, Mr P. V.
(Hard to find the link from phone)

Anyway, with all respect to those who disagree, I'm quite entiteld to think that Kigo would better be functionnal or not be in the distro. Aside I must admit that I do not even know what it function is nor how difficult it would be to eject.

6 members found this post helpful.

That's really uncalled-for.
The "missing" sbokpkg you describe doesn't cause a built-in default package to fail.

13 members found this post helpful.

It's trivial to fix by adding the required engine, and also trivial to remove.

1 members found this post helpful.

With all due respect, AlienBob, your attitude is not right. The issue that OP reported is very minor, but it's a principle thing. And indeed, sbopkg is not part of Slackware, it is not even mentioned on SlackBuilds.org. And finally, the sentences in bold almost sound as if you are mocking him. That's really uncalled for, as already stated.

19 members found this post helpful.

I'm one of those who are waiting patiently for 15.0 to land. Running a fully patched 14.2 (enhanced by quite a few packages from SBo & Alien - for which I'm grateful).

And I was wondering about this. Basically, going "Hmm, wonder what that is". Basically, went to look and discovered that I already had Kigo installed, and the 14.2 version also claims "Kigo was unable to find a Go engine back end".

So, 15.0 RC1 is no more broken that 14.2 regarding this.
I am, however, not interested enough in learning to play go to follow up on Alien Bob's suggestion.

2 members found this post helpful.

It's a minor issue, but I agree with Scrutinizer80. Since Kigo comes with a default Slackware install one would expect it to be functional. GNU Chess is included in Slackware, so why not just include GNU Go too? It's not like it's a big packaging burden either: the last stable release was February 19, 2009

6 members found this post helpful.

Makes me wonder why it isn't part of KDE, since Kigo is a KDE app.

1 members found this post helpful.

My issue with the OP is his high-horse demeanor, not having used Slackware since 3.0 and suddenly barging in that an application needs to be removed from Slackware because it is "broken" because of a "bug". This is not a bug, the package is not broken, it starts fine, but it needs an additional piece of software to work.
Some more examples:
Kamoso, the KDE video recorder, does not work in Slackware because it depends on a piece of functionality in 'gst-plugins-bad' which is not part of standard Slackware. You can find it at SlackBuils.org though.
Slackware's networkmanager is not able to connect to Cisco VPN servers because an openconnect package is not included in Slackware.
Slackware lacks a freerdp package, so krdp is unable to connect to Microsoft servers.

These too are not "bugs", and you - the user - can easily resolve it.
You can extend Slackware's capabilities yourself and should not expect Slackware to do everything for you. There's other distros that will hold your hand.

9 members found this post helpful.

I don't see a person who ends their post with "I almost feel ashamed reporting this, but still" like this. Give it a rest.

14 members found this post helpful.