From owner-freebsd-ports Tue Aug 20 14:59: 2 2002 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9873E37B400 for ; Tue, 20 Aug 2002 14:59:00 -0700 (PDT) Received: from topaz.mdcc.cx (topaz.mdcc.cx [212.204.230.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A5F743E65 for ; Tue, 20 Aug 2002 14:59:00 -0700 (PDT) (envelope-from edwin@mavetju.org) Received: from k7.mavetju (topaz.mdcc.cx [212.204.230.141]) by topaz.mdcc.cx (Postfix) with ESMTP id F1BF02B912; Tue, 20 Aug 2002 23:58:56 +0200 (CEST) Received: by k7.mavetju (Postfix, from userid 1001) id F0D9F6A7124; Wed, 21 Aug 2002 07:58:47 +1000 (EST) Date: Wed, 21 Aug 2002 07:58:47 +1000 From: Edwin Groothuis To: "Thomas E. Zander" Cc: ports@freebsd.org Subject: Re: Why isn't ports/41614 going to be committed? Message-ID: <20020820215847.GC8779@k7.mavetju> References: <20020820075906.GA31501@f113.hadiko.de> <20020820125706.72f9623f.corecode@corecode.ath.cx> <20020820114755.GE31501@f113.hadiko.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020820114755.GE31501@f113.hadiko.de> User-Agent: Mutt/1.4i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Aug 20, 2002 at 01:47:55PM +0200, Thomas E. Zander wrote: > On Tue, 20. Aug 2002, at 12:57 +0200, Simon 'corecode' Schubert wrote > according to [Re: Why isn't ports/41614 going to be committed?]: > > > patience is a virtue. ports committers have lots of things to do and are > > doing stuff in their free time. patches also need to be tested (more or > > less) extensively so that the resulting port builds and runs well. > > if there is no ports committer working with linux-eagle himself, it's > > hard to try out for him.... > > I just wanted to know if there is a specific problem that prohibits the > update to be committed. > I wouldn't ask if it was a compilcated story that breaks dependencies > or something. > So I hope that somebody will take a look at it when he's got enough > time to do it. It's all a YMMV (Your Milage[sp] May Vary)... Sometimes I don't hear of a port for months and when I send an update I get messages saying the original port doesn't work. Sometimes I get a message after a couple of days saying that there are problems. Sometimes people don't want to help with a port because it doesn't look like something they would use, or something which has too many dependencies which frightens them. Complaining here doesn't help (been there, done that), contacting specific commiters about it doesn't help (been there, done that). Contacting the person who did the commit of the previous version looks like a good way to go, that has (for me) the best successrate. Edwin, based on statistics of more than 160 PR's :-) -- Edwin Groothuis | Personal website: http://www.MavEtJu.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/weblog.php bash$ :(){ :|:&};: | Interested in MUDs? http://www.FatalDimensions.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message