From: Detlev Casanova <detlev.casanova@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: brian.dolbec@gmail.com
Subject: [gentoo-soc] Rework porthole for portage API -- week 5
Date: Mon, 27 Jun 2011 23:09:15 +0200 [thread overview]
Message-ID: <21835981.GNQ5iIalnd@naboo> (raw)
[-- Attachment #1: Type: text/plain, Size: 730 bytes --]
Hello,
This last week wasn't a google summer of code week, it was a big exam week. I
managed to do some work on the pkgcore backend but that was nothing exciting :
* Check what functions could be implemented with pkgcore (pkgcore doesn't
provide everything we need in porthole)
* Have a first look of how actions (install, uninstall, update) will be
implemented.
As those 5 first week have been a bit sparse GSoC wise, I'll try to do my best
to catch up the timeline.
This week, I'll continue working on the pkgcore module :
* Implement lib.py functions that can be implemented with pkgcore
* implement actions (install, uninstall, update)
Next step will be to use and debug the portage's api action functions.
Detlev.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2011-06-27 21:09 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=21835981.GNQ5iIalnd@naboo \
--to=detlev.casanova@gmail.com \
--cc=brian.dolbec@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