From: Detlev Casanova <detlev.casanova@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] GSoC -- Week 7
Date: Mon, 12 Jul 2010 17:47:16 +0200 [thread overview]
Message-ID: <201007121747.19750.detlev.casanova@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2278 bytes --]
If you like lists :
Finish a working version of the interpreter
Make the interpreter work with arguments
Make the interpreter work with class instances
Read out the new layman API
Solve a problem that prevents functions from being executed
Create an overlay C class that uses the new layman API
Restructure classes
Add some methods to Overlay, fix some warnings
Implement Config and DbBase
Add a C <-> Python Dict class and fix DbBase to take a Dict for it's config
argument
Get proper layman branch, Check what should really be implemented
Implement the whole LaymanAPI
Get the proper layman Python library and fix BareConfig constructor
Make tester and fix compilation issues
If you don't :
This week, I've decided that the interpreter is the best solution to execute
python code, especially because what's going to be used is a stable Python
API.
I've also written a C version of the layman API Brian Dolbec wrote earlier
this week. It allows doing everything you need to do with Layman :
add/remove/get information from/sync a layman overlay.
The C lib sources can be downloaded on my git repository :
git clone http://soc.dev.gentoo.org/~cazou/c-portage c-portage
There is no building system yet, I'm working on it but having internet
connexion issues does not help at all.
All you'll find in that repository is a 'src' directory. Enter it and type the
compile command line :
gcc -W -Wall -L/usr/lib/python2.6/ -lpython2.6 -I/usr/include/python2.6/ -o
tester --std=c99 -g *.c
and execute ./tester.
I you want it to work, You'll need Brian's Python layman API :
git clone http://dev.gentooexperimental.org/~dol-sen/git/layman.git
and switch to the API branch
git checkout api
(if this last one does not work, try git checkout -b api remotes/origin/api)
You must know that memory management is still crappy and not everything has
been tested.
Brian might also have pushed some updates to the code taht prevents from
syncing an overlay.
Documentation will come but currently, it's the very same as Brian's layman
API.
I also have to speak more, give more details and comment the code more, that's
something I tend not to do and reminding it to me is a very good idea :-)
Detlev.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2010-07-12 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:47 Detlev Casanova [this message]
2010-07-13 16:11 ` [gentoo-soc] Re: GSoC -- Week 7 Detlev Casanova
2010-07-20 9:43 ` [gentoo-soc] Re: GSoC -- Week 8 Detlev Casanova
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=201007121747.19750.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