From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4572 invoked from network); 21 May 2004 18:16:13 +0000 Received: from smtp.gentoo.org (156.56.111.197) by parrot.ussg.indiana.edu with SMTP; 21 May 2004 18:16:13 +0000 Received: from parrot.ussg.indiana.edu ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BREZ3-0006Og-6C for arch-gentoo-dev@lists.gentoo.org; Fri, 21 May 2004 18:16:13 +0000 Received: (qmail 28524 invoked by uid 89); 21 May 2004 18:14:36 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 27625 invoked from network); 21 May 2004 18:14:35 +0000 From: "Christian Gut" Date: Fri, 21 May 2004 20:14:33 +0200 To: gentoo-dev@lists.gentoo.org Message-ID: <20040521181432.GD29108@is-root.org> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <200405201846.37173.cbrewer@stealthaccess.net> <1085145580.8753.93.camel@newkid.milsson.nu> <1085146797.25036.52.camel@localhost> <200405211554.06946.c.j.bainbridge@ed.ac.uk> <1085151850.878.7.camel@gs75.geol.vt.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <1085151850.878.7.camel@gs75.geol.vt.edu> User-Agent: Mutt/1.5.5.1i X-Authenticated-As: cycloon@is-root.org X-Authenticated-As-Hash: 01f3df807ccd9547808ac8b4ae99a0ea Subject: Re: [gentoo-dev] Stuff that makes people mad X-Archives-Salt: ef2abdc3-5508-4d68-a4d5-3b10b0cd67f5 X-Archives-Hash: 3d4693e6f791ce8e2ca8b2f506a071b5 On Fri, 21 May 2004, Stephen Becker wrote: > > > There ought to be some sort of procedure for dealing with user > > submitted ebuilds. I would suggest a system of putting them in ~x86 (or > > whatever) immediately, and if there are no bug reports for x days move them > > to x86. > > > > The problem with this idea is that the developers would lose control on > consistency and quality of ebuilds in portage. Just because you might > be good at writing an ebuild doesn't mean that everyone knows what they > are doing. We could end up having software installed to silly places > and/or non-standard config file storage, which would be very less than > desirable. There is a reason that we are required to take a test to > become developers, part of that being to know what to do and what not to > do when writing ebuilds and/or accepting them to add to portage. I to agree with both sides. But what about integrating an easy way to add custom rsync or perhaps ftp/http repositorys stackable to portage? like debian does it with apt. If there is a user maintaining ebuilds which can't get into the gentoo tree, he sets up his own tree and maintains them there. If others want that ebuilds, they add his tree to their .. make.conf. Yes I know about overlay but i think of a more flexible way... the sites like breakmygentoo could maintain repositories with untested ebuilds and users are on their own testing/using them but it would perhaps help to grow people writing better ebuilds and wanting to becume gentoo devs. I like the debian way doing this. I don't like it for basic things like java or something, but I think this would also help commercial developers integrating their software within gentoo -- gentoo-dev@gentoo.org mailing list