From owner-freebsd-ports@FreeBSD.ORG Wed Aug 5 21:48:24 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CC25106564A; Wed, 5 Aug 2009 21:48:24 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 1A2AD8FC0C; Wed, 5 Aug 2009 21:48:23 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 9C7C48C083; Wed, 5 Aug 2009 16:48:23 -0500 (CDT) Date: Wed, 5 Aug 2009 16:48:23 -0500 From: Mark Linimon To: Alex Goncharov Message-ID: <20090805214823.GB4759@lonesome.com> References: <20090706014719.GG11993@lonesome.com> <070151759cb2aacd36a14eb4b318a435@xs4all.nl> <20090716181711.GC90253@comcast.net> <36957fedc04d840595162bb026a8ec62@xs4all.nl> <20090801114833.GA23826@lonesome.com> <83e5fb980908040459k2e533ab4o2d23b229f98b8ace@mail.gmail.com> <4A785310.6070109@FreeBSD.org> <20090804195441.GA2710@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Cc: trebestie@gmail.com, dougb@FreeBSD.org, freebsd-ports@freebsd.org, carpetsmoker@rwxrwxrwx.net Subject: Re: status of FreeBSD ports you maintain as of 20090705 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 21:48:24 -0000 On Tue, Aug 04, 2009 at 05:44:57PM -0400, Alex Goncharov wrote: > Could do more for the project -- but looks like nobody needs it. Oh, > well, I am not insisting. Persistence is the name of the game. The more PRs you submit, the more you are likely to attract the attention of the existing committers, and that's the track to becoming a new committer. > How a new port would have broken the existing ones? (5.4 is not an > upgrade -- it's a separate port not touching 5.0, 5.1 or 6.0.) - CONFLICTS must be set properly - latest_link must be set properly - the name can't be the exact same as an existing port (kind of equal to latest-link being right) - must be added correctly in category Makefile These are the most common errors people make when adding new ports. Yes, they are all easily learned. > the words "we need more volunteers, committers etc." sound insincere. We have a tremendous backlog of PRs and not all incoming PRs get noticed. However, historically, folks who persist and send a large number of PRs _do_ get noticed. But it doesn't happen overnight. Anyways, I don't think I'm going to be able to change your mind about this topic, so I'll step back and listen to other people's opinions now. mcl