From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9628 invoked by uid 1002); 22 Apr 2003 19:11:02 -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 9567 invoked from network); 22 Apr 2003 19:11:02 -0000 Date: Tue, 22 Apr 2003 21:11:00 +0200 From: Fredrik Jagenheim To: gentoo-dev@gentoo.org Message-ID: <20030422191100.GA10102@pobox.com> Mail-Followup-To: gentoo-dev@gentoo.org References: <1050997108.2986.28.camel@amd.vsen.dk> <1051016369.4102.46.camel@entropy> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1051016369.4102.46.camel@entropy> User-Agent: Mutt/1.5.1i Sender: Fredrik Jagenheim Subject: Re: [gentoo-dev] Ebuilds not getting in :( X-Archives-Salt: 8fd92b2e-4889-4c73-8f2e-094d606f5d38 X-Archives-Hash: 4c8b11b33439d1b270834fb8d4461e06 On Tue, Apr 22, 2003 at 02:59:30PM +0200, Frantz Dhin wrote: > A distribution that prides itself by being flexible and bleeding edge > should also have smooth and flexible policies. For insight into where > bureaucratic policies brings a distribution refer to Debian. While I understand the frustration in not getting feedback on work put down, there's always PORTDIR_OVERLAY. If someone, apart from you, have a need for the latest, greatest version of the package they can always download the ebuild from bugs.gentoo.org and put it locally. I guess some enterprising person with some time on their hands always can do a hack which will keep your PORTDIR_OVERLAY synced to bugs.gentoo.org. Anyways, I don't think the problem stems from ebuilds not being commited to CVS fast enough, but the complete lack of feedback from developers what happens to bugs/ebuilds/fixes that is entered to bugs.gentoo.org. I know developers are busy, but a simple acknowledge from the assigned developer of the status would help calm down the commiters. As of now, many times all what happens to the bug-entry is that you see it gets assigned and then silence... I have personally spent a couple of evenings tracking down long standing bugs and belived that I have reached some sort of solution on them. But since I haven't heard any feedback I'm not sure if someone cares, my fixes were so wrong they didn't even deserve a mention or there is a better fix... Yeah, I know. I spent the first half of this letter telling you that your problem was non-existant, and then spending the other half ranting on my problems as if they were the end of the world. Have mercy on me, I've had a rough day. ;) //H -- To segfault is human; to bluescreen moronic. -- gentoo-dev@gentoo.org mailing list