I didn't read the OP's posts as arrogant (in fact it seemed the opposite to me). Agreed that it's not exactly a "bug", but in any case, I think GNU Go would be a reasonable and lightweight addition that would make Kigo work out of the box, which is a nice thing™.

15 members found this post helpful.

As I see it,

When one installs a complete OS - offline from an iso,
the resulting system - viewed as a whole product, shouldn't require
any extras for basic functionality of its installed components.
That's not to say of course there couldn't be components that can optionally be extended
by installing addons, only that the core functionality should be there.


All the best,
Chris.

3 members found this post helpful.

The fact is that the gnugo software is not maintained since more than 12 years (2009-02-19)
And that the GIT repository is no longer accessible either
http://git.savannah.gnu.org/cgit/gnugo.git

I am not a maintainer of a distribution, but I understand that such software is not included and the freedom to add it or not, remains to the user

He had no high-horse demeanor; quite the opposite. Projection, perhaps? If something is broken when doing a full install, it's a bug. He reported it. Isn't that exactly what is supposed to happen?

14 members found this post helpful.

By the way, to build GNU Go from SBo, gnugo.SlackBuild needs:
after the block setting the SLKCFLAGS. And yes, it's very old and seems to be abandoned (but it does work, and let's you play Go against the computer on Kigo).

4 members found this post helpful.

I am sorry you guys all feel this way. Perhaps it is time for me to consider other pastures.
I have uploaded a "gnugo" package to my repository as a favor, I don't play GO so I don't care but I hope someone finds it useful.

As for me: goodbye and thanks for all the fish. I am taking a break from Slackware and its online communities. I hope for you that Slackware 15.0 will see the light sometime but it seems Pat is unstuck in time. I hope he will un-stick himself and give new life to this great distribution.

3 members found this post helpful.

What did he mean by this?

dear Eric,

we all have our ups and downs in life. I (and I believe I am not alone) hope that things go well for you and that whatever is troubling you stays behind.

Your contributions to Slackware and the community are immense and I am sure there is not a single person in this forum that thinks otherwise.

best,

Petar

21 members found this post helpful.

Maybe this:

It seems that Pat does not go with the arrow of time from past to future continuously like others but keeps jumping to different times in the past or the future. I hope he will get out of it and release Slackware 15.

2 members found this post helpful.

Hear, hear!
Well said!

1 members found this post helpful.

Well, we all greatly appreciate your contributions, and you leaving would be a great loss to Slackware. No doubt about that. I hope you will come back once Slackware 15 is un-stuck.

8 members found this post helpful.

KDE have some frontends as part of DE. F.e. it ships with Cantor which is a frontend to different algebra systems like Octave, Maxima, Scilab, etc. If Pat removes that frontends from KDE, than there will be problems for anybody who want to install that frontend, because one would have to download and build huge KDE sources just to get that tiny frontend. From the other side, choosing between Octave, Maxima, etc is up to user, not maintainer. If Pat will provide maxima package, to make Cantor functional, fans of Octave will be angry. And so on. Provide every algebra system supported by Cantor and every backend for other frontends is a huge overhead. Taking in mind that number of active Cantor or Kigo users is hardly huge, providing already built KDE frontends leaving choice of favorite backend to the user seems reasonable.

All in all, since when building favorite algebra system or GTP engine become the problem for Slackware user?

3 members found this post helpful.

Well, these things are sometimes what it takes to "light a fire under someone's ass" as the saying goes. I was surprised it took this long TBH, but you committed a lot of time and effort to the project and I suspected that there must be some frustration. It's understandable.

Thanks for all you've done to keep -current viable in the absence of a stable release for so long. There were others to be sure, but we would not have KDE Plasma without you, just like I suspect we would not have XFCE4 without Mr. Workman. Or SBO builds for -current without Ponce. etc., etc., etc....

These past few years make one think a lot about what they devote their time to. I support 16 hospitals in my day job and it has been an interesting 20 months.

Do what you must to be happy. Thanks for the fish indeed.

12 members found this post helpful.

I share your disappointment with Slackware's direction over the past years, but it must be extra frustrating after giving so much to the community on an ongoing basis. I hope that the new donation system will help to un-stick the ship. Thanks for all your contributions, have a good break from it all, and hope to see you around once again if you feel like it.

12 members found this post helpful.

Maybe I'm too naive or too patient but I don't really have a problem with the time it's taking for the Full Release. I do recognize that some devs might get frustrated considering Current is IMHO even as a "Snapshot System" substantially better than any previous Full release, but it is Patrick's baby and it should be obvious his standards are extremely high. OTOH it may be valuable to remember that there's always room for 15.1

1 members found this post helpful.