| 1 |
Hi there ! |
| 2 |
I had some troubles last weekend and you therefore did not see a weekly |
| 3 |
report, I'll do it today. |
| 4 |
|
| 5 |
That was a Kuroo bug fixing week. Brian finally could install it and found lots |
| 6 |
of bugs I wasn't aware of. Some where fixed : |
| 7 |
* Crash at startup, |
| 8 |
* Crash when double click on a package, |
| 9 |
* Crash when switching tabs in the package inspector, |
| 10 |
* Kuroo not starting from the K/Gnome menu entry. |
| 11 |
|
| 12 |
One big crash that has not been solved yet is the one at the end of the emerge |
| 13 |
command. It does not happen every time and seems to be cause by Xcb. |
| 14 |
That's for week 8, |
| 15 |
|
| 16 |
For week 9, I tried to solve 2 bugs : |
| 17 |
The first one is the kuroo icon in the system tray that's not showing. I'd like |
| 18 |
people to test it in a Gnome environment if they have that problem under KDE. |
| 19 |
I only succeeded in showing a question mark icon if the kuroo icon is not |
| 20 |
found. |
| 21 |
After digging, I found out that it happens only when kuroo is run without |
| 22 |
kdesu (even using kdesu with your username will fix the problem.) |
| 23 |
I wanted to put the problem on KStatusNotifier but I can't be sure. Maybe the |
| 24 |
icons are not properly installed or not properly detected by kded (though they |
| 25 |
are propery detected by kuroo), which manages the system tray using DBus. |
| 26 |
|
| 27 |
On wednesday, a first version of the portage public api was available. |
| 28 |
You can get it from git : |
| 29 |
|
| 30 |
git clone git://git.overlays.gentoo.org/proj/portage.git |
| 31 |
git branch remotes/origin/public_api |
| 32 |
|
| 33 |
So I was able to start the C portage library. |
| 34 |
You can get it from git: |
| 35 |
|
| 36 |
git clone http://soc.dev.gentoo.org/~cazou/c-portage |
| 37 |
|
| 38 |
Compilation is as usual : configure, make, make install |
| 39 |
|
| 40 |
It's not finished, for instance, the action functions are not implemented yet. |
| 41 |
Also, I've been wondering if returning pointers to Stringlist's is a good |
| 42 |
idea. That means the user has to free it afterwards. |
| 43 |
Some functions returning multiple lists take pointers to pointer to |
| 44 |
StringList. |
| 45 |
|
| 46 |
For example, |
| 47 |
|
| 48 |
StringList* portageGetVersions(const char*, int); |
| 49 |
|
| 50 |
would become |
| 51 |
|
| 52 |
StringList portageGetVersions(const char*, int); |
| 53 |
|
| 54 |
and the StringList wouldn't need to be freed after the function call. |
| 55 |
|
| 56 |
This week, I'll continue working on that library and start integrating in |
| 57 |
Kuroo. |
| 58 |
|
| 59 |
Detlev. |
Archives