It is not user friendly that they install and start kigo and then are informed "Error, Kigo was unable to find a Go engine backend." GnuGo might be a good candidate. See http://www.gnu.org/software/gnugo/download.html Reproducible: Always
We have several similar problems I guess. maybe we can find a way to have an in-advance first run screen for that: "if you want to run this application properly, you need to install [application] [url]" On the other side: kigo itself tells you to install a go engine, or to configure kigo! properly. The question is basically if we want to be a complete software distribution, or if we simply provide you with the KDE software part and you have to install the 3rdparty applications. I started at least an overview in the wiki which we might also want to link somewhere (probably even in the installer). http://techbase.kde.org/Projects/KDE_on_Windows/additional_software_needed
(In reply to comment #1) > We have several similar problems I guess. maybe we can find a way to have an > in-advance first run screen for that: "if you want to run this application > properly, you need to install [application] [url]" > On the other side: kigo itself tells you to install a go engine, or to > configure kigo! properly. > The question is basically if we want to be a complete software distribution, > or if we simply provide you with the KDE software part and you have to > install the 3rdparty applications. The installer is able to fetch and run 3rdparty setup installers from a @package config entry (https://projects.kde.org/projects/kdesupport/kdewin-installer/repository/revisions/master/entry/doc/format-specifications.txt#L137), so 3rdparty installers could be added as package dependency.
Well, there are problems with the 3rdparty dependencies in the installer: - they have to be maintained. It is already hard to update the win32libs dependencies and keep those up to date. - the maintainance cannot be shared that easily - you do at least need a git account to be able to commit that or know how to use git and send patches to the mailing list etc. - to find out for the installer whether a package is installed is also not that easy. This depends on the packaging system of the 3rd party and lies not in our hands. This can become even more complex and would more or less be required then. So I am not really in favor of going that way.