Date: Wed, 7 Jun 2017 22:06:14 +0000 From: "Sergey A. Osokin" <osa@FreeBSD.org> To: Bartek Rutkowski <robak@FreeBSD.org> Cc: Adam Weinberger <adamw@FreeBSD.org>, ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r442588 - in head/www: nginx nginx-full Message-ID: <20170607220614.GB55217@FreeBSD.org> In-Reply-To: <99D58682-8825-417C-81F8-EDC541D31713@FreeBSD.org> References: <201706042038.v54KcQMf001482@repo.freebsd.org> <20170605001807.GA55217@FreeBSD.org> <99D58682-8825-417C-81F8-EDC541D31713@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 06, 2017 at 02:32:17PM +0100, Bartek Rutkowski wrote: > > On 5 Jun 2017, at 01:18, Sergey A. Osokin <osa@FreeBSD.org> wrote: > > > > Hi Bartek and Adam, > > > > I don't think I can get this, so two questions for you guys: > > o) what was the reason to bump PORTREVISION in www/nginx? > > o) wouldn't it btter to just bump PORTREVISION in www/nginx-full? > > Hi Sergey, > > Let me explain it quickly: some time ago you've removed two external modules from www/nginx port, which is a master for www/nginx-full. The www/nginx-full had them in default options, what caused port/pkg build failures and to fix these I needed to remove these two no longer existing modules from default options. After doing so, since it *does* change the contents of the package, I needed to bump the PORTREVISION of www/nginx-full and there were few ways of doing so, but none of them was easy/simple as they were creating even complex scenarios in future bumps/updates, so, after consulting possible solutions with portmgr members, I've chosen one, that while not ideal, have solved the issue for now without creating other issues in future, that is to bump the master www/nginx revision. > > Hope that helps. Hi Bartek, Please don't bump PORTREVISION on www/nginx when you need to do so in www/nginx-full. -- Sergey Osokin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170607220614.GB55217>