From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Portage API
Date: Sun, 17 Oct 2004 20:01:36 +0900 [thread overview]
Message-ID: <200410172001.37303.jstubbs@gentoo.org> (raw)
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@gentoo.org mailing list
next reply other threads:[~2004-10-17 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 11:01 Jason Stubbs [this message]
2004-10-17 16:25 ` [gentoo-portage-dev] Portage API Brian
2004-10-18 13:53 ` Jason Stubbs
2004-10-18 16:14 ` Brian
2004-10-19 1:08 ` Brian
2004-10-23 14:29 ` Jason Stubbs
2004-10-18 18:52 ` Daniel Taylor
2004-10-19 22:56 ` Daniel Taylor
2004-10-20 1:28 ` Brian
2004-10-18 20:08 ` Brian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200410172001.37303.jstubbs@gentoo.org \
--to=jstubbs@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox