From: Brian <dol-sen@telus.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Portage API
Date: Mon, 18 Oct 2004 13:08:17 -0700 [thread overview]
Message-ID: <1098130097.26978.73.camel@localhost> (raw)
In-Reply-To: <200410172001.37303.jstubbs@gentoo.org>
On Sun, 2004-10-17 at 20:01 +0900, Jason Stubbs wrote:
> 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
>
You might want to email pythonhead, he is importing portage and
gentoolkit for his portage frontend named portal. I don't know if he is
on this list.
> --
> gentoo-portage-dev@gentoo.org mailing list
>
--
Brian <dol-sen@telus.net>
--
gentoo-portage-dev@gentoo.org mailing list
prev parent reply other threads:[~2004-10-18 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 11:01 [gentoo-portage-dev] Portage API Jason Stubbs
2004-10-17 16:25 ` 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 [this message]
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=1098130097.26978.73.camel@localhost \
--to=dol-sen@telus.net \
--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