From: Detlev Casanova <detlev.casanova@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: Brian Dolbec <brian.dolbec@gmail.com>,
Andrew Schenck <lane_andrew@hotmail.com>
Subject: [gentoo-soc] Re: GSoC -- Week 8
Date: Tue, 20 Jul 2010 11:43:47 +0200 [thread overview]
Message-ID: <201007201143.50804.detlev.casanova@gmail.com> (raw)
In-Reply-To: <201007121747.19750.detlev.casanova@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1843 bytes --]
Lots of little things this week :
Make functions use the updates in the api
Fix memory management errors, add a construction function for string list
Fix laymanAPIGetInfo() to use a list of tuples
Fix laymanAPIGetInfo() not to crash
Add a function to the layman API to get information from a list of overlays
Add a building system
Check all python objects after a call to Python
Use asserts when PyObject_IsTrue returns -1
Fix libtool system
Add comments where necessary
Implement missing functions : laymanAPIAddRepo, laymanAPIDeleteRepo
Modify the Message class constructor to only take mandatory arguments, other
arguments can be set with the corresponding methods
Add laymanAPIIsRepo, laymanAPIIsInstalled, laymanAPIGetInfosStr,
laymanAPIGetInfoStr, laymanAPIGetAllInfos, laymanAPIAddRepos,
laymanAPIDeleteRepos and overlayInfoFree
Make use of _laymanAPIGetAllInfos() as a common base for both
laymanAPIGetAllInfo() and laymanAPIGetAllInfos()
Add function laymanAPIAddRepo and laymanAPIDeleteRepo
Use correct value when using PyObject_IsTrue
Fix building system and commit it.
Remove obsolete workaround
Put kuroo ebuild on the gentoo overlay server
Add missing file to build c-layman
Hide internal functions in the library
Finish commenting the code.
Fix back PyObject_IsTrue()
Write a live ebuild for c-layman
Doxygenise the functions comments
In short, I've been fixing up the c-layman library.
There is now an ebuild for it which is in the kuroo overlay (layman -a kuroo)
It will soon migrate to the gentoo servers.
This week, I'll go back to kuroo and hunt down and fix bugs that are not due to
command output parsing or package version comparison.
That will be the job of the new portage API for C which Kuroo will use.
And that's it, except if something new comes up.
Detlev.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2010-07-20 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:47 [gentoo-soc] GSoC -- Week 7 Detlev Casanova
2010-07-13 16:11 ` [gentoo-soc] " Detlev Casanova
2010-07-20 9:43 ` Detlev Casanova [this message]
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=201007201143.50804.detlev.casanova@gmail.com \
--to=detlev.casanova@gmail.com \
--cc=brian.dolbec@gmail.com \
--cc=gentoo-soc@lists.gentoo.org \
--cc=lane_andrew@hotmail.com \
/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