svn commit: r335584 - head/www/nginx/files

[Andrej Zverev]

On Fri, Dec 6, 2013 at 8:47 PM, Mathieu Arnold <mat at freebsd.org> wrote:
>
>
> +--On 6 décembre 2013 20:27:05 +0400 Andrej Zverev <az at freebsd.org> wrote:
> | On Fri, Dec 6, 2013 at 7:27 PM, Mathieu Arnold <mat at freebsd.org> wrote:
> |
> |> | Supposedly, the second category of people will get nginx with
> |> | enable-able syslog support from vanilla port at the next update
> |> | of their tree.  SYSLOG_SUPPORT is off by-default, so packages won't
> |> | be affected too.
> |>
> |> Packages built with the default options won't be affected, yes.
> |> But for people not using packages, or building packages with non default
> |> options won't know there is a new version of the port.
> |
> | PHB contains text in a case where this should be done, and when not.
> | I'm with osa@ and rea@ here, you are trying make new rules on the fly.
>
> Well, yes, but the thing is, the system is not perfect, most of updates of
> nginx are a modules/plugins update, and if one wants to have the updated
> version, one has to force the reinstallation of the port, because the
> version has not changed.
Blame pkgng ;-)

>
> For instance, here, I have a few hundreds servers here, I run my own
> poudriere builds so that I can have sane options for the packages I
> install, like for instance, for nginx, SSL, most non third parties modules,
> and a few third parties I need here and there.
> When some nginx module is updated, and I want poudriere to rebuild it, I
> have to go and remove the existing package, so that it gets rebuild. I
> shouldn't have to do that :-)

Oh, you can teach your scripts to look into Makefile's revision and
fire french tinderbox.
At least if you have few hundreds servers you can adapt all for you in
your local playground.
For example, I'm doing build everytime from scratch and within my own
schedule (like I'm not care about version, changes). Updating lot of
servers by every port update looks strange for me.

>
> |> You have to bump PORTREVISION when what you change can change the
> |> package.
> |
> | Then find all your commits (at least for two months) and bump
> | PORTREVISION there for a start ;-)
>
> If I bump perl's PORTREVISION and ask people to rebuild everything, I'm
> going to get lynched :-p
Yes, but why I need to update nginx every time (by your logic) if I
don't use modules which are not default? )


>
> --
> Mathieu Arnold