1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Hi, |
5 |
|
6 |
I think, this is already somewhere on the agenda of portage (perhaps |
7 |
with a low priority ;)), but I nevertheless wanted to ask for the |
8 |
possibility to have as much of emerge's functionality exported in an API |
9 |
as possible =). |
10 |
|
11 |
The reason behind this is, that for Portato (this GUI thingy ;)), I have |
12 |
to re-implement lots of things that portage does (update functionality, |
13 |
parts of dep-string parsing etc). This is kind of sisyphean, because one |
14 |
has to: |
15 |
- - notice/detect subtle changes (esp. the updating process often changes |
16 |
unnoticed in small points) |
17 |
- - support tons of portage versions |
18 |
|
19 |
Especially with larger bumps (2.1.1 -> 2.1.2; -> 2.2) there are lots of |
20 |
things breaking and showing another behavior. |
21 |
|
22 |
In the sum, this work takes quite a large part of the whole development |
23 |
process ... though showing no results for the user ;) |
24 |
|
25 |
Thus, it would be really great, if I only had to use an API (which might |
26 |
change over time - but API changes are easier to track and to work around). |
27 |
Perhaps - as you currently seem to be restructuring the whole thing - |
28 |
you can bundle some things and export them :). I bet there are more |
29 |
people out there besides me, that use or want to use the portage API and |
30 |
would be thankful, when they don't have to reinvent things :) |
31 |
|
32 |
Else - thank you guys for your great work :). It's very great to see |
33 |
portage's evolution over the last months. |
34 |
|
35 |
Regards, |
36 |
René |
37 |
-----BEGIN PGP SIGNATURE----- |
38 |
Version: GnuPG v2.0.9 (GNU/Linux) |
39 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
40 |
|
41 |
iEYEARECAAYFAkiM4ToACgkQ4UOg/zhYFuBx8gCeMU+pZht4rosLNBU32YlSAex3 |
42 |
LyYAnRqVLpguj4i9ZHAcbQEYtTmvSNY+ |
43 |
=F398 |
44 |
-----END PGP SIGNATURE----- |