Bugzilla Bug 82017

Bug fixes and new features.
Changelog:
-View new packages after esync
-Check if su to enable menu actions, and warn if not su
-View latest version in All Packages and Installed packages tabs
-Restoring listviews selected category
-Dependencies tab added in Portage tab.
-World file editable in settings.
-Arch and size columns added to Installed packages.
-Added "Export to world file" in Edit menu.

Created an attachment (id=51226) [edit]
Ebuild for Kuroo-0.53.1

Karim, there's still the QPixmap problem (bug 81633), and bug 82510, too.
For this reason it's better to keep kuroo in package.mask.

There are also other crashes and valgrind shows a huge number of problems,
it would be a great thing if you could find a kde developer willing to 
review your code before further releases. The KApplication/KUniqueApplication 
usage in main.cpp in particular seems really wrong.

One last thing: when submitting ebuilds use the most recent ones that are
already in portage as a template.

Ok!
Could you be more precise regarding KApplication/KUniqueApplication issue?
I see the ebuild in Portage was updated, didn't get notice when that happened.

typo: the QPixmap problem is bug 82633.

> The KApplication/KUniqueApplication usage in main.cpp in particular seems 
> really wrong.

Forget that, it was me not being able to read, sorry.

Hi Gregorio!

I installed for the first time KDE-3.4 (beta2) yesterday to test alleged bugs. So far so good.
Regarding the bugs, I will submit fix to bug 82510, and believe bug 82633 was due to missing 22x22 kuroo pixmap.

Valgrind does report a lot of "memory leaks", but most should be suppressed. Here is what QT support Dimitri says about the subject:
"...
In short, memory leaks usually reported by Valgrind or other memory 
debuggers inside Qt are usually not memory leaks in the strict sense. 
They do produce "noise" though, which doesn't help understanding the 
output of memory debuggers. Maybe this will be fixed in upcoming 
versions of Qt.
..." (See http://lists.trolltech.com/qt-interest/2004-10/thread00381-0.html)

Thanks, you're really fast at addressing bugs!

Created an attachment (id=52325) [edit]
New release of Kuroo: 0.53.1b

Hi Gregorio!
The crashes were due to corrupted stack caused by threads events.
I have run kuroo-0.53.1b for many hours straight without faults on
KDE-3.4.0_beta2 and KDE-3.4.0_rc1.
One new features is added: Package description column.

Ok, a couple notes:

kuroo should be usable without the need to ever touch make.conf.
At the moment it requires "PORTDIR=/usr/portdir" explicitely 
uncommented there.

And it seems the values set in the wizard are never applied.

Yes I guess the textboxes (lineEdits) are confusing.
Below them is stated "All settings are editable later in Kuroo preferences."

Regarding make.conf:
Some users have requested this feature. Having paths both in make.conf and kuroorc is confusing. For example if a user changes settings in make.conf, the risk is kuroo would not function. 
Also having access to make.conf to change build options is quite nice.
Though maybe kuroo should backup make.conf.

> Yes I guess the textboxes (lineEdits) are confusing.
> Below them is stated "All settings are editable later in Kuroo preferences."

You can mark them readonly.

> Regarding make.conf:
> Some users have requested this feature. Having paths both in make.conf and 
> kuroorc is confusing. For example if a user changes settings in make.conf, 
> the risk is kuroo would not function. 
> Also having access to make.conf to change build options is quite nice.
> Though maybe kuroo should backup make.conf.

Sorry, but you can't expect that everyone will run kuroo as root and let it
overwrite /etc/make.conf. You just have to hardcode the default for PORTDIR
if it's not specified in make.conf.

One other thing: when reading and writing back make.conf, kuroo eats the
backslashes (e.g. in the FETCHCOMMAND examples.)

You're right, users should be able to enter settings in intro wizard, it's most
logical. I'll fix that.
"/usr/portage" is already hardcoded as default in settings.kcfg, I'll add a
check to see if PORTDIR is empty in make.conf.
I'll look into backslashes issue.

By the way, I've talked to the author of Kompare about using it as gui to
etc-updating. Just some thoughts...

> "/usr/portage" is already hardcoded as default in settings.kcfg

It does not seem so. It worked in 0.53.0, though.

Created an attachment (id=53191) [edit]
New release of Kuroo: 0.54.0

Added size and description to all listviews.
Fixed bug when kuroo is eating \ when saving back to make.conf.
Added new icon for masked packages.
Gui redesign: results is moved to tabs in mainTabs.

Added to portage. Thanks.