From owner-freebsd-ports@freebsd.org Thu Oct 29 00:37:05 2015 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EF3EA1F8AE for ; Thu, 29 Oct 2015 00:37:05 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from bravo.brtsvcs.net (bravo.brtsvcs.net [IPv6:2001:19f0:300:630e:5400:ff:fe14:a60e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2CDD114C5 for ; Thu, 29 Oct 2015 00:37:05 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from chombo.houseloki.net (unknown [IPv6:2001:558:6025:4b:757f:4f8f:4dc0:401e]) by bravo.brtsvcs.net (Postfix) with ESMTPS id 515BB4F039 for ; Thu, 29 Oct 2015 00:37:03 +0000 (UTC) Received: from [IPv6:2601:1c2:d00:3e10:baca:3aff:fe83:bd29] (unknown [IPv6:2601:1c2:d00:3e10:baca:3aff:fe83:bd29]) by chombo.houseloki.net (Postfix) with ESMTPSA id 388471271 for ; Wed, 28 Oct 2015 17:37:01 -0700 (PDT) To: freebsd-ports@freebsd.org From: Mel Pilgrim Subject: How to follow changes to porting best practices? Message-ID: <56316A26.5040701@bluerosetech.com> Date: Wed, 28 Oct 2015 17:36:54 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2015 00:37:05 -0000 Nearly every time I send a maintainer update, there's some new method I don't know about. There's nothing about it on ports or ports-announce and porttools/portlint don't mention it either. I end up scanning through commits to ports/head/Mk to find them after the fact. What do I need to do to track changes to Ports BCP? It seems subscribing to ports and ports-announce, and using the existing porting tools is insufficient.