From owner-freebsd-ports@FreeBSD.ORG Wed Apr 14 06:27:03 2004 Return-Path: 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 62E9F16A4CE for ; Wed, 14 Apr 2004 06:27:03 -0700 (PDT) Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 2F41543D48 for ; Wed, 14 Apr 2004 06:27:03 -0700 (PDT) (envelope-from adamw@magnesium.net) Received: (qmail 24375 invoked by uid 1252); 14 Apr 2004 13:27:03 -0000 Date: 14 Apr 2004 09:27:03 -0400 Date: Wed, 14 Apr 2004 09:27:03 -0400 From: Adam Weinberger To: Gary Hayers Message-ID: <20040414132702.GE94922@toxic.magnesium.net> References: <20040414061254.GC19749@aurema.com> <200404140615.i3E6Fcf5018886@box.hayers.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200404140615.i3E6Fcf5018886@box.hayers.net> X-Editor: Vim 6.2 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx X-ASL: 6/m/behind you User-Agent: Mutt/1.5.4i cc: 'FreeBSD-Ports' Subject: Re: New port? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2004 13:27:03 -0000 >> (04.14.2004 @ 0215 PST): Gary Hayers said, in 0.7K: << > Christopher Vance wrote: > > On Fri, Apr 09, 2004 at 03:53:29PM +0100, Gary Hayers wrote: > >> I have written my first port and submitted the pr, can anyone please > >> tell me how long it takes to get it placed into the cvs repository? > > > > Mine took 9 months and was broken on arrival. > > > > -- > > Christopher Vance > > Eeks lol. I was hoping to have it in there before the ports freeze. >> end of "RE: New port?" from Gary Hayers << Gary - I've found that in general, the following things tend to delay the addition of a new port: * Any build errors; committers may test it, get frustrated, and give up * Not passing portlint -A * Use of hardware/devices/programs that very few committers to; we want to test stuff, especially from new committers * Many dependencies; this is just a PITA (nothing to be done about these last two items, really) * Any bizarre tricks or manoeuvres in the Makefile, created by not knowing a better way... if you had to guess at anything, check it against other ports * Asking when your port will get committed; I stay away from PRs that generate those requests * Being seen as encouraging people who whine about the crappy treatment they received by committers, like we owe the world some fast response time or something Double-check your port. If it has any technical issues, fix them. And don't feed those who troll. # Adam -- Adam Weinberger adamw@magnesium.net || adamw@FreeBSD.org adamw@vectors.cx || adamw@gnome.org http://www.vectors.cx