Date: Sun, 1 Nov 2015 14:41:42 -0800 From: Mel Pilgrim <list_freebsd@bluerosetech.com> To: Bryan Drewery <bdrewery@FreeBSD.org>, freebsd-ports@freebsd.org Subject: Re: How to follow changes to porting best practices? Message-ID: <56369526.4080208@bluerosetech.com> In-Reply-To: <5631987D.7080809@FreeBSD.org> References: <56316A26.5040701@bluerosetech.com> <5631987D.7080809@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56369526.4080208>