Re: [gentoo-guis] One backend for alle portage GUIs

[René 'Necoro' Neumann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It's going stepwise forward :) Today during some boring university
classes I created a first provider for portage [1]. It is strongly based
on the old backend for portato -- with other words, the API is far from
being considered stable. If you want to take a look at what the current
API is, you find the files under [1] and (as it is not really
documented) some comments here [2]. The comments are not 1:1, but you
should get the idea :)

Further, I created two ebuilds: "app-portage/catapult" and
"app-portage/catapult-portage". You find all info about them in the wiki
[3].

If you want to check the new provider: I have copied the client for the
showcase and changed it to the provider API. You have two possibilities
to start it:

1.) Go into the provider dir: Launch start.py& and then the client.py
2.) Install the two ebuilds (just do "USE='portage' emerge -av
catapult"), then go into the provider dir and launch client.py (Yes -
the daemon is started automatically ... dbus ftw ;P)

At the beginning of next week, I'm planning to make portato use this new
amazing backend :). We'll see if this is going to work... (Rumors say
that currently dbus times out on the first connect...)

Regards,
- - a tired Nec

[1] https://svn.origo.ethz.ch/catapult/portage
[2]
https://svn.origo.ethz.ch/portato/trunk/portato/backend/system_interface.py
https://svn.origo.ethz.ch/portato/trunk/portato/backend/package.py
[3] http://catapult.origo.ethz.ch/wiki/directory_structure_and_ebuilds
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHBXSm4UOg/zhYFuARAiQpAKCFpQV7wHdv8kvVZqpinnUkVhtnowCfXuS3
ZVSn9oR5pgNnUldZsQCmghI=
=4Uoy
-----END PGP SIGNATURE-----
-- 
gentoo-guis@g.o mailing list