How to follow changes to porting best practices?

Mel Pilgrim list_freebsd at bluerosetech.com
Sun Nov 1 22:41:50 UTC 2015


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.


More information about the freebsd-ports mailing list