From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=DATE_IN_PAST_12_24,DMARC_NONE, INVALID_DATE,MAILING_LIST_MULTI autolearn=no autolearn_force=no version=4.0.0 Received: from mailgw3.netvision.net.il ([194.90.1.11]) by cvs.gentoo.org with esmtp (Exim 3.30 #1) id 15stPf-0001Xg-00 for gentoo-dev@cvs.gentoo.org; Sun, 14 Oct 2001 16:07:16 -0600 Received: from there (ras4-p112.rlz.netvision.net.il [62.0.85.240]) by mailgw3.netvision.net.il (8.9.3/8.9.3) with SMTP id AAA16732 for ; Mon, 15 Oct 2001 00:07:36 +0200 (IST) Message-Id: <200110142207.AAA16732@mailgw3.netvision.net.il> Content-Type: text/plain; charset="iso-8859-1" From: Dan Armak Organization: Gentoo Linux To: gentoo-dev@cvs.gentoo.org Subject: Re: [gentoo-dev] A wishlist X-Mailer: KMail [version 1.3.1] References: <20011014184111.04df9895.karltk@prosalg.no> In-Reply-To: <20011014184111.04df9895.karltk@prosalg.no> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: gentoo-dev-admin@cvs.gentoo.org Errors-To: gentoo-dev-admin@cvs.gentoo.org X-BeenThere: gentoo-dev@cvs.gentoo.org X-Mailman-Version: 2.0 Precedence: bulk Reply-To: gentoo-dev@cvs.gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux development list List-Unsubscribe: , List-Archive: Date: Sun Oct 14 16:08:01 2001 X-Original-Date: Mon, 15 Oct 2001 00:06:44 +0200 X-Archives-Salt: 20fc96e8-9922-4f61-a295-12cab525b041 X-Archives-Hash: 79955564f981eb8462d4a51509a750f1 Some followups and suggestions: For the documented portage API: I don't mind it being in python, although c/c++ would be nice sometime down the road. This is a must for all the stuff karltk calls Gentool.Configure. At least, I wish for a short summary of the portage.py api. I tried reading it through; there are no comments at all. For the ebuild review team: They could have several separate Gentoo installs. Maybe in chroots. One would be empty (emerge system only), good for checking depends. Ebuilds are unmerged once they are confirmed to be working. Another would have all existing ebuilds installed, good for checking conflicts. It would also have all revs installed, good for checking upgrades and different dep version scenarios. We could have [at least] two devs on the team, one for each of these configs, running emerges in the background whenever they aren't using the cpu. Say on non-main machines. Of course, there'll probably also be a more standard testing machine. For the ebuild layout (Martin's wish): IMHO one of the best things here, beyond guides and docs, is eclasses. They ensure maximum standardization, and a lot of other fun things too. -- Dan Armak Gentoo Linux Developer, Desktop Team Matan, Israel