From owner-freebsd-ports@FreeBSD.ORG Sat May 17 02:19:15 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03AC8BA3 for ; Sat, 17 May 2014 02:19:15 +0000 (UTC) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id E477820A4 for ; Sat, 17 May 2014 02:19:14 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0N5P0083859BD900@hades.sorbs.net> for freebsd-ports@freebsd.org; Fri, 16 May 2014 19:22:25 -0700 (PDT) Message-id: <5376C71F.90604@sorbs.net> Date: Sat, 17 May 2014 04:19:11 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Kevin Oberman Subject: Re: New/Updated port References: <53763B1A.2020007@sorbs.net> In-reply-to: Cc: FreeBSD Ports ML X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 May 2014 02:19:15 -0000 Kevin Oberman wrote: > > I think the answers to all of this arre found in the Porter's Handbook. > > Submit a PR (using either the send-pr command or the web page > (http://www.freebsd.org/send-pr.html) > > Set the PR as an "Update" OOps put it as 'maintainer update' rather than 'update' ... is that wrong or is it as good as? > > Make the subject one that makes it clear that the PR is an update to a > new version of the port > > The format of the content of the "fix" depends on its size. The > Porter's Handbook discusses this. I just linked my URL rather than trying to persuade my browser to 'shar' it... > > If the maintainer does not respond in a couple of weeks, you might > want to raise the topic on ports, but ports committers are seriously > backlogged, so, even if the maintainer approves the fix (or a modified > version of it), it may take a while to get it committed. (Maintainers > generally are NOT committers.) No worries, thanks for the pointer. Michelle -- Michelle Sullivan http://www.mhix.org/