[gentoo-soc] GSoC -- Week 7

[gentoo-soc] GSoC -- Week 7

[Detlev Casanova]

[-- 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 --]

[gentoo-soc] Re: GSoC -- Week 7

[Detlev Casanova]

[-- Attachment #1: Type: Text/Plain, Size: 2641 bytes --]

On Monday 12 July 2010 17:47:16 Detlev Casanova wrote:
> 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

I changed the location of the repository, it is now in

http://soc.dev.gentoo.org/~cazou/c-layman

so, do a 

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

> 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 :-)

Cheers,

Detlev

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

[gentoo-soc] Re: GSoC -- Week 8

[Detlev Casanova]

[-- 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 --]