I recommend to remove Kuroo from the main ebuild tree. While Kuroo surprisingly received some bug fixes upstream three month ago, it seems to be dead since 2008 (see https://kuroo.org/). At its current state, Kuroo is not simply unstable, but completely unusable for any modern Portage setup. Kuroo is not a simple front-end to Emerge as it claims to be, but re-implements a lot of internal Portage stuff itself. This also includes parsing make.conf. But Kuroo has not kept pace with Portage development. Kuroo relies an deprecated variables such as PORTDIR PORTDIR_OVERLAY DISTDIR PORTAGE_BINHOST etc., to be set in make.conf. Kuroo is not able to handle Portage's modern approach to configure repositories, binarary hosts, umasking of packages and so on through individual files in the directories repos.conf/, binhost.conf/, package.{accept_keywords|mask|unmask|use}/, etc. Basically, Kuroo understands Portage's configuration capabilities as they had been in 2008. Even more dangerous: If one opens the Kuroos configuration dialog and saves the settings, one might very likely break the Portage configuration as Kuroo reconfigures make.conf. As much as I would like to see a graphical front-end for Emerge (or a graphical package manager) and as much as it hurts me to see Kuroo gone, having this package in the ebuild tree suggest hopes which are simply not met.
Karye abandoned it back then but it has been forked and moved to sourceforge as show be HOMEPAGE. We do keep it alive on a lifeline, mostly trying to keep up with changes to KDE/Qt libs, but not quite enough motivation to keep up with all the portage changes. It does rewrite make.conf on using some of the settings pages, but in what way does it break things? The intro dialog also makes backups of everything, check out /var/cache/kuroo/backup/ for those. We plan on working on parsing repos.conf as you mention in the sourceforge bug soon but if there are specific things that are pain points that would be good motivation. Having used it for so many years we're set in our ways and it works well enough that it's hard to see where it is hard for others.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a650ac4ea4e34de586f80ae8b16614fa0a19ec6c commit a650ac4ea4e34de586f80ae8b16614fa0a19ec6c Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2024-07-23 17:48:47 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2024-07-23 17:49:33 +0000 app-portage/kuroo: drop 1.2.2 Assuming 1.2.3 fixed the mentioned problems. (?) Closes: https://bugs.gentoo.org/934211 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> app-portage/kuroo/Manifest | 1 - app-portage/kuroo/kuroo-1.2.2.ebuild | 48 ------------------------------------ 2 files changed, 49 deletions(-)
