From owner-svn-ports-all@FreeBSD.ORG Wed Apr 9 08:06:21 2014 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A73468F3; Wed, 9 Apr 2014 08:06:21 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "plouf.absolight.net", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 65747133B; Wed, 9 Apr 2014 08:06:21 +0000 (UTC) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id A5A06BDC99; Wed, 9 Apr 2014 10:06:19 +0200 (CEST) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) by prod2.absolight.net (Postfix) with ESMTPA id 92649BDC92; Wed, 9 Apr 2014 10:06:19 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by atuin.in.mat.cc (Postfix) with ESMTP id 216C5D35EAE9; Wed, 9 Apr 2014 10:06:19 +0200 (CEST) Date: Wed, 09 Apr 2014 10:06:18 +0200 From: Mathieu Arnold To: Alexey Dokuchaev , Mark Felder Subject: Re: svn commit: r349818 - head/www/nginx Message-ID: <131A373C19AA83C05705C628@atuin.in.mat.cc> In-Reply-To: <20140409060926.GA94220@FreeBSD.org> References: <201404010040.s310e5en074822@svn.freebsd.org> <5342F077.8000105@freebsd.org> <20140409060926.GA94220@FreeBSD.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@FreeBSD.org, Niclas Zeising X-BeenThere: svn-ports-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Apr 2014 08:06:21 -0000 +--On 9 avril 2014 06:09:26 +0000 Alexey Dokuchaev wrote: | [*] Your mentor should have also mentioned that PORTEPOCH bumps should be | generally avoided, as it can never go back (well, there is a way to hack | around it, but it requires renaming the package, which makes it even more | ugly and discouraged). Well, no, it is *not* what a mentor should say. PORTREVISION and PORTEPOCH should be set when they need to be, they should not be avoided because someone think they're ugly. Like the porter's handbook says[1] (at greater lengths that what I'm writing here, but I'm summarizing): PORTREVISION should be increased each time a change is made to the port. It is reset each time PORTVERSION increases. See it as a subversion of a specific version on the port. PORTEPOCH is to be used when PORTVERSION goes back. Say, it goes from 0.19 to 0.2, which, in the upstream developer's mind were really 0.19 and 0.20, but he removed the 0 at the end. And as 0.19 is greater than 0.2, which you can check with: $ pkg version -t 0.19 0.2 > you have to bump PORTEPOCH: $ pkg version -t 0.19 0.2,1 < Because the version of the port *never* decreases. 1: -- Mathieu Arnold