From owner-freebsd-ports@freebsd.org  Sun Nov  1 22:41:50 2015
Return-Path: <owner-freebsd-ports@freebsd.org>
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 8F438A24228
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Sun,  1 Nov 2015 22:41:50 +0000 (UTC)
 (envelope-from list_freebsd@bluerosetech.com)
Received: from delta.brtsvcs.net (delta.brtsvcs.net
 [IPv6:2001:19f0:6000:8e75:5400:ff:fe14:fb98])
 (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 765551188;
 Sun,  1 Nov 2015 22:41:50 +0000 (UTC)
 (envelope-from list_freebsd@bluerosetech.com)
Received: from chombo.houseloki.net (c-73-164-243-16.hsd1.or.comcast.net
 [73.164.243.16])
 by delta.brtsvcs.net (Postfix) with ESMTPS id A54D74EEDE;
 Sun,  1 Nov 2015 22:41:48 +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 58A3B14CC;
 Sun,  1 Nov 2015 14:41:44 -0800 (PST)
Subject: Re: How to follow changes to porting best practices?
To: Bryan Drewery <bdrewery@FreeBSD.org>, freebsd-ports@freebsd.org
References: <56316A26.5040701@bluerosetech.com> <5631987D.7080809@FreeBSD.org>
From: Mel Pilgrim <list_freebsd@bluerosetech.com>
Message-ID: <56369526.4080208@bluerosetech.com>
Date: Sun, 1 Nov 2015 14:41:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101
 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5631987D.7080809@FreeBSD.org>
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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Nov 2015 22:41:50 -0000

On 2015-10-28 20:54, Bryan Drewery wrote:
> On 10/28/2015 5:36 PM, Mel Pilgrim wrote:
>> 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.
>
> I cannot keep up either.
>
> The ideal place is in the /usr/ports/CHANGES file.  It is supposed to
> get news about new framework changes.

I resigned myself to subscribing to src-ports-all and filtering for 
commits to Mk/* and CHANGES.