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