svn commit: r458000 - head/www/nginx

[Sergey A. Osokin]

On Tue, Jan 09, 2018 at 11:49:11AM -0700, Adam Weinberger wrote:
> > On 9 Jan, 2018, at 11:33, Sergey A. Osokin <osa at FreeBSD.org> wrote:
> >
> > On Tue, Jan 09, 2018 at 11:03:35AM -0700, Adam Weinberger wrote:
> >>> On 9 Jan, 2018, at 5:35, Sergey A. Osokin <osa at FreeBSD.org> wrote:
> >>>
> >>> Hello,
> >>>
> >>> is there any update?
> >>>
> >>> Thanks.
> >>
> >> Hi Sergey,
> >>
> >> Sorry, but I can't give you a good answer on why the change was or wasn't
> >> discussed, and why people were or weren't notified about it in advance. It
> >> was policy long before it was written into the PHB, and that occurred in
> >> r43772, 3 years 11 months ago.
> >>
> >> At the end of the day, it's simply the only mechanism we have to ensure
> >> that users' installations match what we have in the repo. Past that I'm  
> >> not
> >> really sure how to give you a satisfactory answer your question. If the
> >> policy were enacted a few months ago, I could provide insight, but we're
> >> talking about something that's been policy for 5+ years.
> >
> > Adam,
> >
> > thanks for the update.
> >
> > Since this new policy never been discussed, we had no public plans to
> > enact this policy in our roadmap, the developers have never been notified
> > about this major change, I'd recommend to postpone it and start new  
> > discussion.
> > Personally I don't see big value of it, also I think this new policy
> > potentially can bring more harmful than positive effects for the project.
> 
> Come on, Sergey. We cannot postpone something that's been active policy for  
> OVER FIVE YEARS.

So we didn't here about that for so long period of time? :-)  Could
please explain this.

> Users need to rebuild a port when it changes. It doesn't matter which set  
> of options they're using, they must rebuild it. If you'd like to have a  
> discussion about changing the policy, then that's great and we should have  
> that discussion. But in the meantime, you MUST follow the policy.

Fortunately I'm not on a position to follow an dictate like this, so I'm
going to avoid to use this policy as I did for all of those years.

-- 
Sergey Osokin