From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12803 invoked from network); 17 Oct 2004 10:59:28 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 17 Oct 2004 10:59:28 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CJ8l6-00044E-7b for arch-gentoo-portage-dev@lists.gentoo.org; Sun, 17 Oct 2004 10:59:28 +0000 Received: (qmail 14515 invoked by uid 89); 17 Oct 2004 10:59:27 +0000 Mailing-List: contact gentoo-portage-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-portage-dev@lists.gentoo.org X-BeenThere: gentoo-portage-dev@gentoo.org Received: (qmail 22414 invoked from network); 17 Oct 2004 10:59:26 +0000 From: Jason Stubbs To: gentoo-portage-dev@lists.gentoo.org Date: Sun, 17 Oct 2004 20:01:36 +0900 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200410172001.37303.jstubbs@gentoo.org> Subject: [gentoo-portage-dev] Portage API X-Archives-Salt: 6d11e0c5-4271-4f1c-afcc-664ae36f7ead X-Archives-Hash: 722f18fd74a2bfce15b015aea3e12b1a 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