Thans for your answer, I'll investigate that stuff. But currently more important for me is, where else in the web I can find informations about the updates in the portage tree. As I said, I can parse packages.gentoo.org, but it contains much overhead. ViewPortageX currently is used at least on 500 systems, but there come more and more. It would put some load on the server when I let the theme fetch so many information from packages.gentoo.org as I need it to do.
So, perhaps somebody knows how I can do this more efficiently. > Perhaps you may find portholes code easier to find out how to obtain > info from portage. The portagelib.py file is where all portage > interaction takes place. Since the devs know about what it uses already > it is probably the safest code taps from portage to use. You should be > able to get all the info you need from those examples. > > Also you may want to keep track of pkgcore_lib.py. It is the next > generation portage code that will be coming our way. I have only just > started integrating it for porthole (my first commit of it last night). > Many things will change by the time the code is ready for general use, > but will give you an idea of how to plan ahead. The tree structure is > quite a bit different than current portage. I know I will need to re-do > a bunch of porthole's code to be optimized for the new structure. Also > it should be faster. So far, just building all the available packages > from the local tree as well as all installed packages is about 1 sec. > faster on my machine, probably better again when it's ironed out. If > there is something lacking in it's API, Brian Harring wants to know. > > -- > Brian <[EMAIL PROTECTED]> -- gentoo-portage-dev@gentoo.org mailing list
