1 |
On Sun, 2010-03-21 at 23:14 +0100, Patrick Lerner wrote: |
2 |
> On Sat, 2010-03-20 at 09:02 -0700, Brian Dolbec wrote: |
3 |
> > [..] As for it not being pushed in the main tree, Zac |
4 |
> > informed me that there were some problems with it that needs a proper |
5 |
> > API in portage for it to be stable and reliable. He also intends to |
6 |
> > implement it ( as have others in previous years), but he is only one |
7 |
> > person, already busy with the core development of portage. |
8 |
> > |
9 |
> > If there is to be a project to with portage it should be the |
10 |
> > implementation of a proper public API for apps to use such as porthole, |
11 |
> > portato, himerge, etc.. |
12 |
> |
13 |
> Is there like any information out on how the communication between |
14 |
> client and portage would work? As in "Portage Daemon" or something along |
15 |
> the lines of python bindings? |
16 |
> In case I can help (with no previous experiences on creating public |
17 |
> APIs), I'd be glad to do so even outside the scope of SoC. |
18 |
|
19 |
The portage public API is mostly coded in the form of the packagekit |
20 |
portage backend which was one of last years soc projects. The |
21 |
packagekit bacend is in the gnome overlay if you want to look it over. |
22 |
It is in 2 basic parts, 1 a "c" to python bridge to access the python |
23 |
based portage interface code. It is this interface code that is to be |
24 |
integrated into portage proper as a public API. |
25 |
|
26 |
I talked with zmedico about the portage public API and he said that it |
27 |
does not need much modification to be a part of portage. With some |
28 |
recent code changes and split-ups, portage is now ready for more API |
29 |
integration. He will be doing it in the near future and plans it for a |
30 |
2.1.9 release. |
31 |
|
32 |
> |
33 |
> > If you want to work on a gtk |
34 |
> > interface, I could always use more help with porthole, Necoro is |
35 |
> > extremely busy with schooling and could use help with portato. I |
36 |
> > haven't talked with araujo enough to know if he needs help with himerge. |
37 |
> |
38 |
> I've looked into Porthole, which looks pretty similar to what I had in |
39 |
> mind when proposing a GTK portage front-end, so I'm going to look into |
40 |
> it a bit more. |
41 |
> Something I've actually wanted to do is having some kind of |
42 |
> background-process which would take care of syncing your tree and inform |
43 |
> you about outstanding updates similar to the update managers of Ubuntu |
44 |
> or Windows (systray icon + notify, like evolution does it with new |
45 |
> mail). |
46 |
|
47 |
I've wanted to do this for some time now too :) |
48 |
|
49 |
Also I am starting a complete rewrite of porthole's backend structure |
50 |
that will be able to make proper use of that new API, not to mention be |
51 |
easier to create a pkgcore backend as well. Help is welcomed and |
52 |
appreciated. Other things on my TODO list are full layman support, |
53 |
individual overlay tree listings, full binpkg support, possibly even |
54 |
multiple repo source support, py3k readiness, as pygtk is planned to add |
55 |
python-3 support this spring... |
56 |
|
57 |
> In Porthole all I found was the big upgrade button which immediatly |
58 |
> installed everything without even giving me a list of which updates are |
59 |
> there. |
60 |
|
61 |
Ah, when it presented you with the small dialog box asking if you wanted |
62 |
all pkgs in your world file updated you clicked "Yes". Had you clicked |
63 |
"NO" or selected the "Upgradable Packages" view ( that box next to |
64 |
"View:" on the left, right above the category listings. It would have |
65 |
shown you "ALL" the pkgs that have an upgrade available. From that view |
66 |
the "Upgrade" button only upgrades the pkgs that have been selected. |
67 |
|
68 |
Use the Help ==> Contents menu options to open your browser to the html |
69 |
help files installed with porthole. They give you a good overview of how |
70 |
it works and it's capabilities. ;) |
71 |
|
72 |
|
73 |
> Nevertheless, kudos on the project, I'll look into contributing |
74 |
> something to it if I can, too. |
75 |
> |
76 |
> --Patrick Lerner |
77 |
> |
78 |
> |
79 |
|
80 |
I look forward to hearing from you. IRC channels are #gentoo-guis, |
81 |
#porthole |
82 |
|
83 |
-- |
84 |
Brian Dolbec <brian.dolbec@×××××.com> |