Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
Hi all,
Most will know that I worked on and mostly completed an API for portage and
that I've had it to throw it away due to being directly counter to portage's
future goals. Thus, an API has been pushed back to the release following
2.0.51. So, what I need is a list of things that are required of portage from
a client application writer's perspective.
A couple of goals for the API:
* Loose enough to not inhibit portage's direction
* Light enough that it is easy to maintain
* Simple enough that the way to do things is obvious
* Minimilist enough that there is only one way to do things
So, let the suggestions roll. :)
Regards,
Jason Stubbs
--
gentoo-portage-dev@g.o mailing list
|
|
