From owner-freebsd-ports@FreeBSD.ORG Tue May 11 16:19:09 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA3FA106566B for ; Tue, 11 May 2010 16:19:09 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (ns0.infracaninophile.co.uk [81.187.76.162]) by mx1.freebsd.org (Postfix) with ESMTP id 578768FC1B for ; Tue, 11 May 2010 16:19:08 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id o4BGJ2r9064002 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 11 May 2010 17:19:03 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4BE98376.10505@infracaninophile.co.uk> Date: Tue, 11 May 2010 17:19:02 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Christer Edwards References: <20100511013700.GA34279@magic.hamla.org> <201005110409.22796.avilla@freebsd.org> <20100511025234.GB34736@magic.hamla.org> In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.96 at happy-idiot-talk.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL, SPF_FAIL autolearn=no version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on happy-idiot-talk.infracaninophile.co.uk Cc: "freebsd-ports@FreeBSD.org" , Sahil Tandon Subject: Re: ccache 3.0 port 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: Tue, 11 May 2010 16:19:10 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/05/2010 16:46:00, Christer Edwards wrote: > should I post the current portlint-approved Makefile someplace for > further consideration, or should I go about a process of submitting > it? If the latter, what is the appropriate way to submit a new/updated > port? If you can build ccache-3.0, install it and deinstall it without any plist problems, then the port is ready for submission. Well, the new version of ccache you build should actually work properly as well... To submit an update, generate a diff against the previous version of the port using 'diff -Nur'. Attach this to a PR 'send-pr -a port.diff' - -- fill in the fields in the PR as sensibly as possible: the Severity and Priority fields have become rather debased so just set them to 'serious' and 'medium' respectively. Category is 'ports'. If you were the maintainer of the port, Class would be 'maintainer update'; as you aren't the Class should be 'change request' (which is correct in this case, even if one of the changes is to make yourself maintainer). Tag the subject line of the PR with '[patch]' (or '[maintainer]' as appropriate), the port location relative to /usr/ports (ie. "devel/ccache") and a short description of the change: eg "update to 3.0". You don't really need to put anything in the 'How to Repeat' section, nor do you really need to put much in the 'Description' section, but I think it useful to supply links to any changelogs or lists of fixed bugs or similar so people can see what this update includes. If your update adds or removes or renames files in the port, it's good to enumerate those changes in the description of the PR, as this will be a great deal of help to the commmitters. As you aren't maintainer of this port, your PR will be passed to the port maintainer for approval. You may be asked to fix any problems, or the maintainer may have reason to reject your update. Rejection of a straight version update is unlikely. Mostly maintainers will be grateful that someone has volunteered to do the work of generating it. Given the port maintainer is a committer, he might commit changes himself; otherwise it will be passed back to one of the usual set of ports committers. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvpg3YACgkQ8Mjk52CukIxH1wCeOMh6kbsE80/Pc+YeUTL05LYC 6hEAnAk/ap90JmthlC4m5tuqPW+uiKyh =P4Q1 -----END PGP SIGNATURE-----