From owner-svn-ports-head@freebsd.org Sat Mar 19 15:43:33 2016 Return-Path: Delivered-To: svn-ports-head@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 E4AE5AD6331; Sat, 19 Mar 2016 15:43:33 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C215DCD; Sat, 19 Mar 2016 15:43:32 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [192.168.1.22] (249.red-81-37-208.dynamicip.rima-tde.net [81.37.208.249]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 0710A43BD5; Sat, 19 Mar 2016 10:43:22 -0500 (CDT) Subject: Re: svn commit: r411385 - head/www/lighttpd/files To: Jan Beich , Dirk Meyer References: <201603190938.u2J9cF4c014563@repo.freebsd.org> Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Reply-To: marino@freebsd.org From: John Marino Message-ID: <56ED7396.4050104@marino.st> Date: Sat, 19 Mar 2016 16:43:18 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Mar 2016 15:43:34 -0000 On 3/19/2016 11:18 AM, Jan Beich wrote: > Dirk Meyer writes: > Can you bump PORTREVISION ? According to Porter's Handbook > > PORTREVISION must be increased each time a change is made to the port > that changes the generated package in any way. That includes changes > that only affect a package built with *non-default options*. Is that true? It's open for interpretation, and I've never interpreted it that way. I've seen other use the same rationale (doesn't affect packages with default options) as a reason not to bump. If all things are perfect, I agree with you, but people get pretty upset when a port rebuilds for a weak reason. Making something huge rebuild to help out people that customize the port might be "weak" in that sense. In any case, the above interpretation is news for me. John