public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Detlev Casanova <detlev.casanova@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] GSoC : week 8 and 9 : Two in one.
Date: Tue, 3 Aug 2010 20:23:45 +0200	[thread overview]
Message-ID: <201008032023.49780.detlev.casanova@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2275 bytes --]

Hi there !
I had some troubles last weekend and you therefore did not see a weekly 
report, I'll do it today.

That was a Kuroo bug fixing week. Brian finally could install it and found lots 
of bugs I wasn't aware of. Some where fixed : 
 * Crash at startup,
 * Crash when double click on a package,
 * Crash when switching tabs in the package inspector,
 * Kuroo not starting from the K/Gnome menu entry.

One big crash that has not been solved yet is the one at the end of the emerge 
command. It does not happen every time and seems to be cause by Xcb.
That's for week 8,

For week 9, I tried to solve 2 bugs :
The first one is the kuroo icon in the system tray that's not showing. I'd like 
people to test it in a Gnome environment if they have that problem under KDE.
I only succeeded in showing a question mark icon if the kuroo icon is not 
found.
After digging, I found out that it happens only when kuroo is run without 
kdesu (even using kdesu with your username will fix the problem.)
I wanted to put the problem on KStatusNotifier but I can't be sure. Maybe the 
icons are not properly installed or not properly detected by kded (though they 
are propery detected by kuroo), which manages the system tray using DBus.

On wednesday, a first version of the portage public api was available.
You can get it from git :

	git clone git://git.overlays.gentoo.org/proj/portage.git
	git branch remotes/origin/public_api

So I was able to start the C portage library.
You can get it from git:

	git clone http://soc.dev.gentoo.org/~cazou/c-portage

Compilation is as usual : configure, make, make install

It's not finished, for instance, the action functions are not implemented yet.
Also, I've been wondering if returning pointers to Stringlist's is a good 
idea. That means the user has to free it afterwards.
Some functions returning multiple lists take pointers to pointer to 
StringList.

For example,

	StringList*             portageGetVersions(const char*, int);

would become

	StringList             portageGetVersions(const char*, int);

and the StringList wouldn't need to be freed after the function call.

This week, I'll continue working on that library and start integrating in 
Kuroo.

Detlev.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

                 reply	other threads:[~2010-08-03 18:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008032023.49780.detlev.casanova@gmail.com \
    --to=detlev.casanova@gmail.com \
    --cc=gentoo-soc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox