1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Brian schrieb: |
5 |
> On Wed, 2007-10-10 at 19:47 +0200, René 'Necoro' Neumann wrote: |
6 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
7 |
>> Hash: SHA1 |
8 |
>> |
9 |
>> René 'Necoro' Neumann schrieb: |
10 |
>> |
11 |
>> Ok - I've added the current API to the wiki [1]. I did not manage to |
12 |
>> include all of the needs of porthole, as I don't know what some of the |
13 |
>> calls do, and whether they are really needed ;). |
14 |
>> Please see the attached file for the comments. |
15 |
>> |
16 |
>> @dol-sen: Would be great if you could scan through the list and see, |
17 |
>> which ones are really needed. Because portage calls inside functions |
18 |
>> that are then moved into catapult don't need to have an equivalent in |
19 |
>> the API (at least in most cases). - And for the vast majority I was just |
20 |
>> clueless ^^. (and too lazy to lookup portage code). |
21 |
> |
22 |
> |
23 |
> Yeah, I know... I made the list only for reference as to the calls to |
24 |
> portage used. To know what they are used for, etc. you need to go thru |
25 |
> portagelib. Many of the ones needed you already have blank defs for and |
26 |
> raise NotImplemented ERROR. I didn't expect you to implement them all |
27 |
> now anyway :) |
28 |
> |
29 |
|
30 |
Oh oh ... it seems like we are mixing things up here ... Please do not |
31 |
refer to the Portato Code anymore. The only important thing is the |
32 |
catapult code [1] and the API documentation. Sorry if I confused you all =| |
33 |
|
34 |
> |
35 |
>> There are certain issues with the current API: |
36 |
>> |
37 |
>> 1.) Add some more stuff needed by other frontends. |
38 |
>> 2.) Perhaps merge the Package and the System object as they both just |
39 |
>> provide functions. |
40 |
> |
41 |
> I had a chance to look over your code a little more. I think it would |
42 |
> be less confusing if some of the files and classes were renamed. You've |
43 |
> used package.py and class XXXPackage several times. It gets confusing |
44 |
> with a frontend's Package class... Since they are just function groups |
45 |
> then perhaps |
46 |
> |
47 |
> class CPVFunctions |
48 |
> |
49 |
> Anyway, I have some ideas on how we might organize groups of functions, |
50 |
> but I need more time to think it thru and get them down in print. |
51 |
> |
52 |
|
53 |
As I said: Ignore portato's code. ;). And the naming of the classes is |
54 |
really arbitrary - we might change this if you want. What is more |
55 |
important is the DBus-Object Path... |
56 |
|
57 |
>> 3.) Merge package.is_in_overlay() and package.get_overlay_path() |
58 |
>> 4.) Get rid of the different get_*_settings functions and add special |
59 |
>> ones: get_homepage, get_depend(which), get_arch, ... |
60 |
>> 5.) Currently there are two functions returning use flags which were set |
61 |
>> at installation time of a package: |
62 |
>> - get_use_flags(): Returning ALL set useflags |
63 |
>> - get_installed_use_flags(): Return only the set useflags which are |
64 |
>> also in IUSE. |
65 |
>> This should perhaps be merged into one function with an attribute |
66 |
>> "only_iuse" or similar. |
67 |
>> |
68 |
>> Some comments are appreciated ;) |
69 |
>> |
70 |
>> - - Necoro |
71 |
> |
72 |
> Sorry, I have to work again tonight. I won't have time to look yet. |
73 |
> Only enough time to respond with this email. |
74 |
> |
75 |
|
76 |
- - Necoro |
77 |
|
78 |
[1] https://svn.origo.ethz.ch/catapult/portage/catapult_portage/ |
79 |
-----BEGIN PGP SIGNATURE----- |
80 |
Version: GnuPG v1.4.7 (GNU/Linux) |
81 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
82 |
|
83 |
iD8DBQFHDbQd4UOg/zhYFuARAi4TAJ45M1hT94FiRmxnZZymu9ID5NcYIACeI6ZC |
84 |
KYfWtnM1mPRY5w5YygBc8xs= |
85 |
=1KFQ |
86 |
-----END PGP SIGNATURE----- |
87 |
-- |
88 |
gentoo-guis@g.o mailing list |