1 |
Hey everyone ! |
2 |
|
3 |
This week, I've been working on the PackageWrapper class. more and more |
4 |
functionalities have been moved and porthole now uses those instances |
5 |
everywhere. |
6 |
|
7 |
Note that they are used to represent a particular ebuild. For example, the |
8 |
package list gets its information from a list of str's then, PackageWrappers |
9 |
instances are taken from the backend with functions like get_installed(), |
10 |
get_masked(), get_best(),... |
11 |
|
12 |
Now that it is pretty stable, I'll start working on the portage backend again |
13 |
to make it use the PackageWrapper system. |
14 |
|
15 |
Another thing I've been doing is converting the commands file for pkgcore to |
16 |
use the pkgcore scripts, it was using portage's so far. |
17 |
|
18 |
Next week, I plan on working on the portage backend and make it work again. |
19 |
There is also som caching to do, to avoid having multiple copies of the same |
20 |
PackageWrapper (two calls to the same function with the same argument will |
21 |
create 2 identical PackageWrapper, which contains all package properties) |
22 |
|
23 |
I'd also like, if I'm able to stabilize the backends enough, to start working |
24 |
on actions. |
25 |
Even if portage's ones aren't ready, I can already start that. |
26 |
|
27 |
cheers, |
28 |
|
29 |
Detlev. |