| 1 |
On Friday 04 March 2005 20:08, Ian Leitch wrote: |
| 2 |
> Chris White wrote: |
| 3 |
> | I'm putting this here for informative purposes as to achieving proper |
| 4 |
> | parsing of portage for use in extending the already present behaviour to |
| 5 |
> | better suit one's needs. A few things I'll bring into the table from my |
| 6 |
> | experience: |
| 7 |
> |
| 8 |
> Sorry to spoil your post Chris, but I think this is just another |
| 9 |
> testimonial to how badly we all need that portage API (plus the portage |
| 10 |
> daemon for tools such as Porthole who currently also have to parse |
| 11 |
> emerge output). This is by no means the first attempt at parsing I've seen. |
| 12 |
|
| 13 |
I've asked several times before but I may as well ask again. What are the |
| 14 |
requirements? From my point of view, there is not much point in doing |
| 15 |
anything without some specific requirements. Take the analogy of a teenage |
| 16 |
daughter asking her parents for a transportation vehicle. A tractor would fit |
| 17 |
the bill as would a Boeing 747... |
| 18 |
|
| 19 |
Regards, |
| 20 |
Jason Stubbs |
| 21 |
-- |
| 22 |
gentoo-dev@g.o mailing list |
Archives