From owner-svn-ports-all@FreeBSD.ORG Wed Apr 9 06:09:26 2014 Return-Path: Delivered-To: svn-ports-all@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id A576BDE3; Wed, 9 Apr 2014 06:09:26 +0000 (UTC) Date: Wed, 9 Apr 2014 06:09:26 +0000 From: Alexey Dokuchaev To: Mark Felder Subject: Re: svn commit: r349818 - head/www/nginx Message-ID: <20140409060926.GA94220@FreeBSD.org> References: <201404010040.s310e5en074822@svn.freebsd.org> <5342F077.8000105@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) 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 06:09:26 -0000 On Tue, Apr 08, 2014 at 09:32:42AM -0500, Mark Felder wrote: > I'm not entirely sure, but maybe I misunderstood the behavior. Here was > the chain of events: Presuming that your mentor had explained[*] to you the differences between PORTVERSION, DISTVERSION, PORTREVISION, and PORTEPOCH, > - Update made to www/nginx that should require a PORTREVISION bump > - Couldn't bump PORTREVISION and remove PORTEPOCH Could you explain what exactly do you mean by "couldn't bump PORTREVISION"? What prevented it from getting bumped? > - Bumped PORTEPOCH instead [*] 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). ./danfe